From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.7.0-0.2
Date: Sat, 04 Feb 2017 17:16:00 -0000 [thread overview]
Message-ID: <20170204171610.GZ8905@calimero.vinschen.de> (raw)
In-Reply-To: <9c3c4a5420073990b4172637884debfd@smtp-cloud6.xs4all.net>
[-- Attachment #1: Type: text/plain, Size: 2615 bytes --]
On Feb 4 15:56, Houder wrote:
> On Sat, 4 Feb 2017 14:00:15, Corinna Vinschen wrote:
> [snip]
>
> > Bug Fixes
> > ---------
> > - Fix handling of Alt-Numpad sequences in console handler.
> > Addresses: https://cygwin.com/ml/cygwin/2017-01/msg00135.html
> >
> > - Fix erasing UTF-8 multibyte characters in cooked mode.
> > Addresses: https://cygwin.com/ml/cygwin/2017-01/msg00299.html
>
> To be "comsumed" on Monday ...
>
> Hi Corinna,
>
> This time I decided to test with alt-1 and alt-254 as input ... Output is not
> as expected, I would say ...
>
> R. Henri
>
> =====
> Using the Windows Console (cp437):
>
> 64 LANG = en_US.UTF-8, LC_ALL =
> => LANG = en_US.UTF-8
> /home/corinna/src/cygwin/cygwin-2.7.0/cygwin-2.7.0-0.2.x86_64/src/newlib-cygwin/winsup/cygwin/cygheap.cc
> 64-@@ cygcheck -sv | awk '$1 ~ /^(bash|libreadline.|cygwin|"cygwin1.dll")$/'
> "cygwin1.dll" v0.0 ts=2017-02-03 21:17
> bash 4.4.12-3 OK
> cygwin 2.7.0-0.2 OK
> libreadline7 7.0.1-1 OK
>
> # enter alt-1, followed by lf
> 64-@@ ☺
> bash: ☺: command not found
> # enter alt-254, followed by lf
> 64-@@ [G■ <==== expected one character ...
> bash: [G■: command not found
> # enter alt-254, followed by 3 bs, followed by lf
> 64-@@ <==== no problem
>
> 64-@@ bash --noediting # disable readline
> => LANG = en_US.UTF-8
>
> # enter alt-254, followed by 3 bs, followed by lf
> 64-@@
> bash: $'\E\E': command not found <==== knock, knock, who is this?
>
> # enter alt-254, followed by 3 bs, followd by '| od', followed by lf
> 64-@@ echo | od -tx1z
> 0000000 1b 1b 0a >...<
> 0000003
> 64-@@ exit
> exit
>
> 64-@@ dash
> # enter alt-1 followed by lf
> $ ☺
> dash: 1: ☺: not found
>
> # enter alt-1, followed by bs, followed by lf
> $ <==== no problem
>
> # enter alt-254, followed by lf
> $ [G■
> dash: 3: [G■: not found
Works fine for me in dash as well as in od in a console with cp437:
$ od -tx1
<alt-1><^J><^D>
☺
0000000 e2 98 ba 0a
0000004
$ od -tx1
<alt-1><bs><^J><^D>
0000000 0a
0000001
$ od -tx1
<alt-254><^J><^D>
■
0000000 e2 96 a0 0a
0000004
$ od -tx1
<alt-254><bs><^J><^D>
0000000 0a
0000001
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-04 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 13:26 Corinna Vinschen
2017-02-04 14:57 ` Houder
2017-02-04 17:16 ` Corinna Vinschen [this message]
2017-02-04 18:07 ` Houder
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=20170204171610.GZ8905@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).