public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 22:51:00 -0000	[thread overview]
Message-ID: <CAA5t8Vo9Q7kfYpZDLJmWxRDNkq6AcMoZ+vmWFMq3aMJ8i+EUvw@mail.gmail.com> (raw)
In-Reply-To: <CAA5t8VrLdfux66CegQTR1XcGCs8QXPtKZ1m9BU8YeUVitTYqgA@mail.gmail.com>

On Wed, Dec 14, 2016 at 1:33 PM, David Karr <davidmichaelkarr@gmail.com> wrote:
> On Wed, Dec 14, 2016 at 12:06 PM, Thomas Wolff <towo@towo.net> wrote:
>> I've checked with Caffeine and traced mintty. It receives F15 key down, the
>> key up. Caffeine claims to send key up only but that's not true. Please
>> report this as a bug to Caffeine.
>
> Understood.  I just did that.  However, will that really make any
> difference? If mintty only receives the keyup event, will that make it
> ignore it entirely?

I think I have a solution. I've looked at the command line options for
caffeine many times, and I never noticed the "-useshift" option, which
makes it use the shift key instead of f15.  That should do the trick
for me. I'm testing it now, and it appears to be fine (and it also
doesn't appear to cause trouble if I'm typing while the event is
emitted).

--
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

  reply	other threads:[~2016-12-14 22:51 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
2016-12-14 20:07   ` Thomas Wolff
2016-12-14 21:33     ` David Karr
2016-12-14 22:51       ` David Karr [this message]
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=CAA5t8Vo9Q7kfYpZDLJmWxRDNkq6AcMoZ+vmWFMq3aMJ8i+EUvw@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).