From: David Karr <davidmichaelkarr@gmail.com>
To: cygwin@cygwin.com
Subject: Re: mintty window gets tilde characters "pressed" in it
Date: Wed, 14 Dec 2016 17:49:00 -0000 [thread overview]
Message-ID: <CAA5t8Vrwo8v1QNTkn94OgvsZv=2OMecbT4+L2z=wEco5LYtuaw@mail.gmail.com> (raw)
In-Reply-To: <CAA5t8VpHom_Kyy6AnBd+1z=AsKPMWcECpyeXVW_ttT4vvvxaFg@mail.gmail.com>
On Mon, Dec 12, 2016 at 10:18 AM, David Karr <davidmichaelkarr@gmail.com> wrote:
> Win7. I believe my Cygwin version info is "2.5.2(0.297/5/3) 2016-06-23 14:29".
>
> I've been annoyed for a while with a symptom in my mintty windows. I
> will be typing along, or not, and suddenly a "~" character gets
> injected into the stream. It often is the only character at the
> prompt, so I can erase it and type my command, but it's really
> annoying when it appears while I'm typing. I was just reminded of it
> now when it injected the "~" right before I pressed enter on a
> "mkdir", so I had to then remove the dir I just created and recreate
> it.
>
> Is this something that Cygwin can control?
I've determined what "instigates" this, but I find that it only mainly
affects mintty and somewhat affects emacs. I've never seen a symptom
in any other application.
I use a tool called "Windows Caffeine" that is used to keep the
display awake. It sends a "f15 key up" event every 59 seconds. That
is what is producing the "~" character in the mintty window. I've
also seen a symptom from this in Emacs, but it's harder to produce.
It's not as simple as just having a text buffer in focus. I haven't
been able to reliably produce it in Emacs, but the mintty symptom is
very reproducible.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-12-14 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 18:18 David Karr
2016-12-14 17:49 ` David Karr [this message]
2016-12-14 20:07 ` Thomas Wolff
2016-12-14 21:33 ` David Karr
2016-12-14 22:51 ` David Karr
2016-12-14 20:20 ` Andrey Repin
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='CAA5t8Vrwo8v1QNTkn94OgvsZv=2OMecbT4+L2z=wEco5LYtuaw@mail.gmail.com' \
--to=davidmichaelkarr@gmail.com \
--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).