On Fri, 5 Sep 2003 Fergus wrote:
> > Put it at the end so that the UNIX commands
> > wouldn't override MS commands with the same
> > name.
>
> > My question is, was this a foolish and stupid thing
> > to do?
>
> In my opinion: putting it in the PATH is a wise and sensible thing to do,
> giving you access to all this excellent stuff. But (my recommendation would
> be - others may differ): put it before the Windows command pathnames. There
> are very few clashes (find, sort, a couple of others I think) and the Cygwin
> interpretations are incomparably "better" (more useful, versatile,
> informative, helpful).
...and break existing batch files, which expect Windows commands instead.
If you want Cygwin's find, just run "bash -c find". Ditto for "sort",
etc. IMO, of course.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
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/
