From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.3-3
Date: Tue, 01 Aug 2017 19:02:00 -0000 [thread overview]
Message-ID: <cdfa7759-a2ff-9375-076b-c1bb903922cf@redhat.com> (raw)
In-Reply-To: <87d18fktkd.fsf@Rainer.invalid>
[-- Attachment #1.1: Type: text/plain, Size: 1287 bytes --]
On 08/01/2017 01:54 PM, Achim Gratz wrote:
> Steven Penny writes:
>> Could you link to Davids post? I do not see it for this month or July, and I
>> dont seem to have trouble with numlock on or off, even with July 31 version.
>
> She can't, this was a discussion on IRC.
The gist of the conversation and today's patch: when numlock is on,
'alt-5' behaves as expected; but when numlock is off, 'alt-5' was
generating two keypresses at once (the escape sequence for ALT+keypad5
as on Linux when you release keypad5, AND the windows behavior of
injecting a codepoint after releasing alt). Corinna's patch means you
can no longer bind alt-keypad5 to do something magic (this is because
the cmd behavior is that alt-keypad sequences work regardless of numlock
state); but doesn't stop you from binding ctrl-keypad5 or shift-keypad5.
Yes, it means one place where cygwin can't completely emulate Linux;
but the thought on IRC was that more users are probably familiar with
windows alt-sequence codepoint generation than they are with Linux
alt-keypress bindings, and that less than 1% of the population would
even notice the difference.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-01 19:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 19:53 [ANNOUNCEMENT] Updated: libreadline7-7.0.3-3, libreadline-devel-7.0.3-3 Eric Blake (cygwin)
2017-03-25 0:46 ` Steven Penny
2017-04-13 19:07 ` [ANNOUNCEMENT] Updated: libreadline7-7.0.3-3 Steven Penny
2017-04-14 8:27 ` Eric Blake
2017-04-15 10:59 ` Steven Penny
2017-05-15 18:21 ` Eric Blake
2017-05-15 20:46 ` Chet Ramey
2017-06-18 15:53 ` Steven Penny
2017-07-04 21:53 ` Steven Penny
2017-07-27 21:37 ` Eric Blake
2017-07-27 21:39 ` Eric Blake
2017-07-27 21:46 ` Steven Penny
2017-07-28 8:28 ` Eric Blake
2017-07-28 14:55 ` Steven Penny
2017-07-28 18:31 ` Eric Blake
2017-07-28 18:39 ` Steven Penny
2017-07-28 23:55 ` Eric Blake
2017-07-29 1:55 ` Cygwin.bat (was: [ANNOUNCEMENT] Updated: libreadline7-7.0.3-3) Achim Gratz
2017-07-29 2:48 ` [ANNOUNCEMENT] Updated: libreadline7-7.0.3-3 Doug Henderson
2017-07-29 4:23 ` Steven Penny
2017-07-30 18:38 ` Doug Henderson
2017-07-30 19:54 ` Steven Penny
2017-07-29 8:45 ` Steven Penny
2017-07-29 10:08 ` Eric Blake
2017-07-31 18:36 ` Corinna Vinschen
2017-07-31 20:01 ` Steven Penny
2017-07-31 20:05 ` David Macek
2017-07-31 21:13 ` David Macek
[not found] ` <20170731200146.GD18950@calimero.vinschen.de>
[not found] ` <20170731211327.GG18950@calimero.vinschen.de>
2017-08-01 0:56 ` Steven Penny
2017-08-01 8:45 ` Corinna Vinschen
2017-08-01 14:48 ` Corinna Vinschen
2017-08-01 18:20 ` Steven Penny
2017-08-01 18:54 ` Achim Gratz
2017-08-01 19:02 ` Eric Blake [this message]
2017-08-01 7:22 ` David Macek
2017-08-01 8:46 ` Corinna Vinschen
[not found] ` <160b3569-d448-1898-3dcd-b7133a772527@SystematicSw.ab.ca>
2017-08-01 8:44 ` Corinna Vinschen
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=cdfa7759-a2ff-9375-076b-c1bb903922cf@redhat.com \
--to=eblake@redhat.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).