From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Console doesn't work correctly under anything else than cmd or mintty
Date: Sat, 16 May 2020 06:10:58 -0600 [thread overview]
Message-ID: <ffbdd0c9-aa08-cfaf-4b18-d9df18a8dcac@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200516135825.8bc4b6bbba4579750cf667f0@nifty.ne.jp>
On 2020-05-15 22:58, Takashi Yano via Cygwin wrote:
> On Fri, 15 May 2020 14:57:14 -0600
> Brian Inglis wrote:
>>> cygcheck -k
>>
>> This key check works only in a console window, _NOT_ in a terminal session!
>> Abort with Ctrl+C if in a terminal session.
>
> Now cygcheck -k works in pty in a limited way due to pseudo
> console support if the OS is Win10 1809 or later.
But the results are not comparable: under mintty <Backspace>q gives:
$ cygcheck -k
This key check works only in a console window, _NOT_ in a terminal session!
Abort with Ctrl+C if in a terminal session.
Press 'q' to exit.
Pressed 1x VK: 0x0048 VS: 0x0023 C: 0x0008 CTRL: -- -- -- LC -- -- -- -- --
Released 1x VK: 0x0048 VS: 0x0023 C: 0x0008 CTRL: -- -- -- LC -- -- -- -- --
Released 1x VK: 0x0011 VS: 0x001d C: 0x0000 CTRL: -- -- -- -- -- -- -- -- --
Pressed 1x VK: 0x0051 VS: 0x003c C: 0x0071 CTRL: -- -- -- -- -- -- -- -- --
Released 1x VK: 0x0051 VS: 0x003c C: 0x0071 CTRL: -- -- -- -- -- -- -- -- --
whereas under cmd we see:
> cygcheck -k
This key check works only in a console window, _NOT_ in a terminal session!
Abort with Ctrl+C if in a terminal session.
Press 'q' to exit.
Released 1x VK: 0x0008 VS: 0x000e C: 0x0008 CTRL: -- -- -- -- NL -- -- -- --
Pressed 1x VK: 0x0051 VS: 0x0010 C: 0x0071 CTRL: -- -- -- -- NL -- -- -- --
Released 1x VK: 0x0051 VS: 0x0010 C: 0x0071 CTRL: -- -- -- -- NL -- -- -- --
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2020-05-16 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 20:26 Kacper Michajlow
2020-05-13 8:50 ` Eric Lilja
2020-05-13 10:34 ` Takashi Yano
[not found] ` <CABPLASQf4L0WN6wOFd2C6=6ZY1hM9mCL6LaNLsQRa4yGbP6=Mw@mail.gmail.com>
2020-05-14 3:33 ` Takashi Yano
2020-05-14 17:48 ` Kacper Michajlow
2020-05-14 23:47 ` Takashi Yano
2020-05-15 9:34 ` Kacper Michajlow
2020-05-15 11:45 ` Takashi Yano
2020-05-15 15:41 ` Kacper Michajlow
2020-05-15 20:57 ` Brian Inglis
2020-05-16 4:58 ` Takashi Yano
2020-05-16 12:10 ` Brian Inglis [this message]
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=ffbdd0c9-aa08-cfaf-4b18-d9df18a8dcac@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).