From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin 3.1.2 + Windows 10 Home Build 10.0.18362 - alt+space hotkeys not working
Date: Sun, 29 Dec 2019 16:23:00 -0000 [thread overview]
Message-ID: <7b4a1ce2-1634-a42b-70f4-4818d96a087c@Shaw.ca> (raw)
In-Reply-To: <20191228210458.91766a71f16c1392d9c7a4fe@nifty.ne.jp>
On 2019-12-28 05:04, Takashi Yano wrote:
> On Fri, 27 Dec 2019 12:19:53 +0500, Eugene Klimov wrote:
>> i don't use ConEmu
>> but after upgrade to cygwin 3.1 this team have same bugs
>
> These are not the same issue at all. As for alt-space,
> the keycode 0x1b 0x20 is passed to the cygwin application
> correctly inside of console window. This is not a bug.
>
> The issue of ConEmu is that the no key code is passed
> by arrow keys or del key to the cygwin application.
>
>> also rollback cygwin to 3.0 return previous behaviors
>> and GNU `screen` inside cygwin `ssh` works fine
>
> I cannot get what is your problem. I logged in to a linux
> machine using cygwin ssh and start GNU screen in the ssh
> session, however, everything works fine for me. I tried
> that in both mintty and command prompt.
>
> *Please* let us know the *detail* of the steps to reproduce
> your issue and what happens.
He is using some Cyrillic locale:
https://monosnap.com/file/gBqrKZLH4zhquuNWPSTJfHRMJzlMq8
so some more details might help from:
$ mintty -V
Ignoring unknown option 'CharNarrowing'.
mintty 3.0.2 (x86_64-pc-cygwin)
© 2013/2019 Andy Koppe / Thomas Wolff
License GPLv3+: GNU GPL version 3 or later
There is no warranty, to the extent permitted by law.
$ echo $LANGUAGE
en_CA:en_GB:en
$ for o in -s -u -f -i -n ''; do locale $o; done
en_US
en_US
en_CA
en_CA
en_CA
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_ALL=
--
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.
--
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
prev parent reply other threads:[~2019-12-29 5:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 12:20 Eugene Klimov
2019-12-25 12:57 ` Takashi Yano
2019-12-25 13:33 ` Eugene Klimov
2019-12-25 14:46 ` Eugene Klimov
2019-12-25 18:46 ` Takashi Yano
2019-12-25 22:05 ` Eugene Klimov
2019-12-26 10:28 ` Andrey Repin
2019-12-26 17:45 ` Eugene Klimov
2019-12-26 19:18 ` Takashi Yano
2019-12-26 20:16 ` Brian Inglis
2019-12-27 5:00 ` Eugene Klimov
2019-12-27 5:00 ` Eugene Klimov
2019-12-27 5:29 ` Eugene Klimov
2019-12-27 12:34 ` Marco Atzeri
2019-12-27 15:04 ` Eugene Klimov
2019-12-28 13:40 ` Takashi Yano
2019-12-29 16:23 ` 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=7b4a1ce2-1634-a42b-70f4-4818d96a087c@Shaw.ca \
--to=brian.inglis@shaw.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).