From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: mintty phantom key presses
Date: Tue, 3 May 2022 07:19:44 +0200 [thread overview]
Message-ID: <55c9c2b8-ccab-db63-1cf2-6d989c581260@towo.net> (raw)
In-Reply-To: <CAA=0bEORh1+OiRZOWz5HVYCfDUM8kjF54EXeWvtnYsCij6vfBA@mail.gmail.com>
Am 02.05.2022 um 23:54 schrieb Eric Adams:
> Hi,
>
> I had previously reported this issue as "Possible phantom control-key state..."
>
> I observe that moving between cygwin mintty windows and Windows
> windows causes unexpected behavior in the cygwin world.
>
> I took a new approach, using vi :) . In cygwin, I open a new file,
> enter insert mode, hit Ctrl-V, and mouse out of the window. When I
> mouse back into the cygwin edit window, my screen contains the display
> string "^[[O" (note that the "^[" is vi-speak for "esc"). Examining
> the resulting file with od shows:
>> od -ah fdsa
> 0000000 esc [ O nl
> 5b1b 0a4f
>
> Here, the nl character is inserted by vi.
>
> This smells like an incomplete escape sequence. If it's left at the
> command line, just waiting for the user to type something, there might
> be trouble.
>
> Am I completely off?
> Thanks,
> Eric Adams.
CSI O is the focus off notification (CSI I is the focus in notification).
Someone has switched on focus reporting mode (CSI ? 1004 h) in your
session (and isn't catching the notifications).
Run your application in a fresh mintty, with no other software, to test.
Thomas
next prev parent reply other threads:[~2022-05-03 5:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:54 Eric Adams
2022-05-03 5:19 ` Thomas Wolff [this message]
2022-05-03 11:50 ` Eric Adams
2022-05-03 11:53 ` Thomas Wolff
2022-05-03 12:26 ` Eric Adams
2022-05-03 14:02 ` Thomas Wolff
2022-05-03 14:27 ` [cygwin] " Jason Pyeron
2022-05-04 17:57 ` Eric Adams
2022-05-04 18:04 ` Jason Pyeron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55c9c2b8-ccab-db63-1cf2-6d989c581260@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).