From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.1-1
Date: Thu, 12 Jan 2017 18:48:00 -0000 [thread overview]
Message-ID: <1fb2c5f5-80d9-44b1-300b-d59c8df92b25@gmail.com> (raw)
In-Reply-To: <58742d35.43029d0a.29fa1.0df9@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]
On 10. 1. 2017 1:39, Steven Penny wrote:
> On Sun, 18 Dec 2016 09:41:29, Corinna Vinschen wrote:
>> - Fix regression in console charset handling
>> Addresses: https://cygwin.com/ml/cygwin/2016-10/msg00000.html
>
> It looks like fixing this may have caused another issue. Example test:
>
> With cmd.exe, you can type Alt 234 and it produces
> GREEK CAPITAL LETTER OMEGA U+03A9. However with Cygwin via Cygwin.bat it yields
> nothing. Non ASCII characters can be read from scripts, but they cannot be
> entered interactively.
>
> They cannot be pasted either; pasting some words will remove all non ASCII
> characters.
>
> I believe this to be a recent issue, if memory serves this did work before, and
> should given that cmd.exe handles it fine.
My experience:
conhostv2+cmd: Shift+Ins -> ŕ
conhostv2+cmd: Alt+234 -> ŕ
conhostv2+cygwin260+bash: Shift+Ins -> ŕ
conhostv2+cygwin260+bash: Alt+234 -> ŕ
conhostv2+cygwin261+bash: Shift+Ins -> ŕ
conhostv2+cygwin261+bash: Alt+234 ->
(i.e. nothing)
conhostv2+cygwin261+bash: Alt+5 -> [G
(if there's nothing written yet on the input line, Alt+5 also causes what seems to be ~10-second delay in input processing)
mintty+cygwin261+bash: Shift+Ins -> ŕ
mintty+cygwin261+bash: Alt+234 -> ê
Versions and settings:
$ uname -a
CYGWIN_NT-10.0 mew 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin
$ uname -a
CYGWIN_NT-10.0 mew 2.6.1(0.305/5/3) 2016-12-16 11:55 x86_64 Cygwin
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=
$ /proc/cygdrive/c/Windows/System32/chcp.com
Active code page: 65001
Using the font Consolas.
--
David Macek
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3715 bytes --]
next prev parent reply other threads:[~2017-01-12 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 0:39 Steven Penny
2017-01-10 20:08 ` Brian Inglis
2017-01-11 0:00 ` Steven Penny
2017-01-11 6:51 ` Brian Inglis
2017-01-11 12:52 ` Steven Penny
2017-01-11 17:54 ` Brian Inglis
2017-01-11 19:37 ` Steven Penny
2017-01-11 20:41 ` Eliot Moss
2017-01-11 23:19 ` Steven Penny
2017-01-11 23:22 ` Eliot Moss
2017-01-11 23:29 ` Steven Penny
2017-01-11 21:41 ` Brian Inglis
2017-01-11 23:27 ` Steven Penny
2017-01-11 1:35 ` Michael Enright
2017-01-12 14:23 ` John Hein
2017-01-12 18:48 ` David Macek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-18 8:43 Corinna Vinschen
2016-12-21 19:10 ` David Stacey
2016-12-21 20:38 ` 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=1fb2c5f5-80d9-44b1-300b-d59c8df92b25@gmail.com \
--to=david.macek.0@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).