Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <427F5F27.5010507@byu.net>
Date: Mon, 09 May 2005 07:01:27 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Carlo Florendo <list-subscriber AT hq DOT astra DOT ph>
CC: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com
Subject: Re: Strange-Dangerous behaviour in Cygwin
References: <20050507160035 DOT GA12676 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT OSF DOT 4 DOT 21 DOT 0505081445440 DOT 24779-100000 AT ax0rm1 DOT roma1 DOT infn DOT it> <20050508225258 DOT GA3896 AT trixie DOT casa DOT cgf DOT cx> <427ED590 DOT 9080309 AT hq DOT astra DOT ph> <427ED946 DOT 4070001 AT hq DOT astra DOT ph>
In-Reply-To: <427ED946.4070001@hq.astra.ph>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Carlo Florendo on 5/8/2005 9:30 PM:
> Ooops.   Sorry, I've read earlier discussions on this issue just a few
> seconds ago by Erik Blake et al.   So, it's not an xterm issue.  It's a
                 ^^^^
I spell it Eric.

> bug with coreutils not being POSIX compliant.  A patch has been
> applied.  We just have to wait for the next annoucement for coreutils.

Hold on there - the bug in POSIX non-compliance was that before coreutils
patch, `rm -i' accepted " y" as yes, now CVS coreutils obeys POSIX and
interprets it as a match failure (which has the same effect as typing an
answer interpreted as no).  Unfortunately, POSIX requires that if your
terminal settings are strange (such as the ctlecho settings that cgf
mentioned on linux), such that raw editing characters escape the terminal
into the program, that "y\bn" ('y', BACKSPACE, 'n') be interpreted as yes.

The only way this would be an xterm bug is if the default tty settings of
xterm under cygwin can be changed to improve user experience by making it
less likely that raw backspaces are passed through to the program, rather
than being line edited first.

And my next release of cygwin coreutils-5.3.0-6 will not be CVS coreutils
(with all its recent patches in many other areas as well), but stock 5.3.0
with a minimal subset of CVS patches backported as needed (I plan to wait
until 5.3.1 is released before cygwin officially sees all upstream patches
since 5.3.0, unless someone can convince me of a need for cygwin to track
CVS).  That means I will not be changing the yes/no behavior in my next
drop of coreutils.  But rest assured that I am tracking CVS changes on my
own machine, to try and make sure that there are no regressions introduced
when 5.3.1 is finally released upstream.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCf18n84KuGfSFAYARAliCAJ9LHbOYO3swwmsLrqlDff0KMyEY4ACeMzAI
x1/ti+7xCZub+fRYc0Kts6Q=
=wTHd
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/