X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type; q=dns; s=default; b=fGEv csiH4Xr2Fq+fwBHUn4PSZfATsDiNo7DDxpFGJetiBskCrVT4UGK+7z1rJAfpP+oR /gcX7vTmCZH08tREp8DCUpU6xgvD2lZUL4WIJCFOrUeMoaJ2ytMfwe8C2TrFIVZq XtHOET0gSebTTq/wh4WuRlv1u2lCxWp19GwpXzM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type; s=default; bh=XwXJDLZvDe sNSSoHRjL7qZ+rFjE=; b=dR6ESOyvr/0sksl2EmuhPW+9sMW6YGWXgFpIXe1Acd BxkewHru2CBp5mu1z+8KMBQbReM4k6ZIOwtH7cQhfs6As9Gv7XW4dHEgEOsv1Qg8 bg8MfqgtFyX9OirMul9OQdw8ReDNnbWRrVcScbcpYrenHaknqErZZPVkDCjGPFIt w= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.1 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=consoles, H*MI:sk:587eb89, H*i:sk:587eb89, H*f:sk:587eb89 X-HELO: mx1.redhat.com Subject: Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1 To: cygwin AT cygwin DOT com, svnpenn AT gmail DOT com References: <587eb89a DOT 03339d0a DOT 1c944 DOT bffb AT mx DOT google DOT com> From: Eric Blake Openpgp: url=http://people.redhat.com/eblake/eblake.gpg Message-ID: <22d8cd67-3a5a-9f7f-9e4a-eb0a43bd5b2c@redhat.com> Date: Tue, 17 Jan 2017 20:08:17 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <587eb89a.03339d0a.1c944.bffb@mx.google.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NnngJxFsmIJaMW4FTgKRMMS2r86Im3euC" X-IsSubscribed: yes --NnngJxFsmIJaMW4FTgKRMMS2r86Im3euC Content-Type: multipart/mixed; boundary="knR3NFaOS1iabqAIajad40NPvNUseg5WQ"; protected-headers="v1" From: Eric Blake To: cygwin AT cygwin DOT com, svnpenn AT gmail DOT com Message-ID: <22d8cd67-3a5a-9f7f-9e4a-eb0a43bd5b2c AT redhat DOT com> Subject: Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1 References: <587eb89a DOT 03339d0a DOT 1c944 DOT bffb AT mx DOT google DOT com> In-Reply-To: <587eb89a DOT 03339d0a DOT 1c944 DOT bffb AT mx DOT google DOT com> --knR3NFaOS1iabqAIajad40NPvNUseg5WQ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable [again, your email client likes to break threading, so I nearly missed this one] On 01/17/2017 06:36 PM, Steven Penny wrote: > On Mon, 16 Jan 2017 19:32:19, Steven Penny wrote: >> I did another bisect on the readline-7.0-testing branch and came up with= this: >> ef27d114778ffef483ed2746603f9487f880edbd is the first bad commit >> commit ef27d114778ffef483ed2746603f9487f880edbd >> Author: Chet Ramey >> Date: Thu Jul 9 16:28:21 2015 -0400 >> readline-7.0-alpha distribution >=20 Are you building readline from source each step of the bisection? And are you applying all the downstream cygwin patches each build, or just using the stock upstream sources? (The cygwin patches can be found in /usr/src if you use setup.exe to download the sources) > This still works on Linux, even with libreadline7. Linux doesn't have a cmd.exe. And in mintty, I'm having no problems entering extended characters (well, there, ALT-6-6 gives 'B' as in ASCII, but ALT-2-3-4 gives '=C3=AA' instead of '=CE=A9', while ALT-+-2-3-4 = gives '=CE=A9', but at least input isn't silently dropped). So I really think th= is is an issue with interacting with the native windows console (which is cygwin's domain), and not with the input being fed to readline (readline is reading the terminal presented by cygwin, but it is cygwin that is interpreting the console's reaction to keypresses in a way that is converted to what cygwin apps think is a normal terminal). Another thing I tried: running bash in mintty, this command: printf $'\u66\u3a9' outputs 'f=CE=A9' (correct, since hex 66 is 'f', while decimal 66 is 'B'). But while running bash directly from cmd.exe, the same command results in 'f\u03A9'. It's as if bash has determined (from locale?) that the current character set is not Unicode, and therefore outputs an escape sequence instead of the UTF-8 sequence. So next I tried LANG=3Den_US.UTF-8. After that, the printf produced the results I got in mintty, but ALT-2-3-4 caused \316 to be output. Normally, I _don't_ run anything under cmd.exe (all my use of cygwin is under mintty), so I need a lot of hand-holding to reproduce anything in your setup, in particular how you are even getting extended characters to print (what locales and/or window settings you have to set). > Chet is refusing to address > the issue: >=20 > http://lists.gnu.org/archive/html/bug-readline/2017-01/msg00001.html I didn't even know bug-readline existed (all the readline bug reports I've seen over the years have been addressed to bug-bash); I'm subscribed now. But Chet is right that it is probably a Cygwin problem, and not a readline problem. >=20 > So it looks like we will need a Cygwin specific patch? Well, first someone has to get to the real root cause. Since I have been unable to reproduce it, and I don't have much free time to devote to it, I don't know when that will be. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --knR3NFaOS1iabqAIajad40NPvNUseg5WQ-- --NnngJxFsmIJaMW4FTgKRMMS2r86Im3euC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJYfs4RAAoJEKeha0olJ0Nqd90H/1J/TOEyXm7ql2JIcBuGKiWk sdGDFTCOnSKIhhDYYUcGNHscL64LKvjzddTer5X2alcYqYpWrb1rtnVxxG/qkvkZ StIbQjJMkH6rrhSZM4N4wkKuKcBXvxXPK0Sq9hhlA5nSZFSHxOJEUp0AucZYlgEq fjT0mg8E6XYO4EfTKfW1I9zcD14feEk/NCcwBlqfX5c303AeZWOJs/fxiZ+sKpfc MSBsS/xZ3Jm043jvvY/VrQ6LLbIH/P5mIk5RmpVh3LDDc2k3i0y9UD9b8qcdYpPt hK+9LcMQbKRYoruB4G48y0JWCSfy8S/s301+mKgNXnk+YsBP+wahUIj3DGVLBaQ= =J4b0 -----END PGP SIGNATURE----- --NnngJxFsmIJaMW4FTgKRMMS2r86Im3euC--