Mail Archives: cygwin-developers/2000/04/03/07:36:04
IMO, it is simply bad practice to install any tool in such as way as to
modify/break the behaviour of existing tools (including batch files). We
are aware of the issue with find.exe and we should avoid causing
problems for anyone.
> -----Original Message-----
> From: cygwin-developers-owner AT sourceware DOT cygnus DOT com
> [mailto:cygwin-developers-owner AT sourceware DOT cygnus DOT com]On Behalf Of
> Parker, Ron
> Sent: 31 March 2000 22:31
> To: cygwin-developers AT sourceware DOT cygnus DOT com
> Subject: RE: Windows 9x environment space solution
> > From: Chris Faylor [mailto:cgf AT cygnus DOT com]
> > That's fine with me. I would eventually like a solution which set
> > environment variable globally since a lot of people seem to be
> > this but it doesn't have to happen now.
> > And, I don't think that it is likely that people will be complaining
> > they can't use their Windows "FIND" command once cygwin is
> > three years of reading the cygwin mailing list, I don't think I've
> > seen someone complain that a cygwin utility was shadowing a
> I use the cygwin tools at work to solve many different problems and
> frequently deploy a subset of them within a group here. Typically for
> something that can be solved quickly with a script. No one knows
> come from because there is a serious Unix/Linux phobia around here.
> working on that.) However, some of the Professional Engineers around
> think they are developers and they use "many highly sophisticated
> files, that I just wouldn't understand". (Try not to laugh when
> tells you that.) I caught some serious backlash for putting the cygwin
> binaries in the PATH and "changing default behavior of the operating
> system." I guess it made me gun shy.
> The people that use the cygwin mailing list are a little more
> computer savvy than my normal "target audience".
- Raw text -