This is the mail archive of the
mailing list for the cygwin project.
RE: upgrade advice for end users
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'it's simple really.'" <cygwin-talk at cygwin dot com>
- Date: Sun, 7 Jan 2007 19:33:34 -0000
- Subject: RE: upgrade advice for end users
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On 06 January 2007 23:11, Gary R. Van Sickle wrote:
>> From: Dave Korn
>> Sent: Saturday, January 06, 2007 3:44 PM
>> To: Thread TITTTL'd!
>> Subject: FW: upgrade advice for end users
>> On 05 January 2007 23:49, fschmidt wrote:
>>> Having just suffered through a cygwin upgrade, I would like to let
>>> other end users know what they need to do to get cygwin to work.
>> Note how he implicitly believes that the only possible way
>> for something to work is however he imagines it should work,
> Which is totally different from your position... how exactly?
My position is that if it works in /any/ valid way, it is "working" in the
common-or-garden sense, and that if you want an *authoritative* definition of
'valid', you go look up the specs, rather than indulge in wish-fulfilment. In
short, I don't think anything was "broken" either before *or* after the recent
change to bash's CR handling, and to describe it as so is a purely pejorative
use of the word. Since I don't think either one was broken, I don't claim any
special status for whichever way round happens to be to my personal taste.
So, that would be different from his position.... how exactly? By a
hundred and eighty degrees different, that's how.
Can't think of a witty .sigline today....