Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<01c901be6dc1$6447dee0$cf39a5d1@www.lightspeed.net>
From:	"David's Lightspeed Email" <dpainter AT lightspeed DOT net>
To:	"Suhaib M. Siddiqi" <Ssiddiqi AT InspirePharm DOT Com>,
	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	re: find
Date:	Sat, 13 Mar 1999 18:21:37 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.2106.4
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.2106.4

                                    March 13th, 1999

The MS-DOS "find" is, I agree, useless.
As for the "Windows" "find", found in the Windows Explorer Tools menu and
also accessible by pressing F-3 normally, this is actually a decent tool.

                                     David L. Painter
                                     dpainter AT prontomail DOT com
                                     dpainter AT lightspeed DOT net
                                     ph: (559) 292-5366 * 3
                                     fax:(559) 292-0410
-----Original Message-----
From: Suhaib M. Siddiqi <Ssiddiqi AT InspirePharm DOT Com>
To: Rick Rankin <rrankin AT primenet DOT com>
Cc: cygwin AT sourceware DOT cygnus DOT com <cygwin AT sourceware DOT cygnus DOT com>
Date: Saturday, March 13, 1999 5:23 PM
Subject: Re: find, ksh, and job control


>
>-
>
>>But are there really enough command name conflicts to justify all that? I
>>haven't really checked, but the only one I'm really aware of is find, and
>>the windows find command is pretty useless anyway.
>
>After a little back and forth writing you are basically syaing the same
>thing
>*Windows find is useless.*
>
>If you have Windows Nt UNIX option pack installed then there are a whole
lot
>of conflicts if you add Cygwin to your WinNT path.
>
>>Personally, I am
>>perfectly happy putting the cygwin bin in my path ahead of windows or
>winnt,
>>but if there are other name clashes, perhaps another method is warranted.
>>
>
>If I rememebr correctly, a while ago, some user wrote he deleted cmd.exe
and
>replaced is by bash.exe.  I think it is all personal preferences what you
>like to see, do and are used to of.
>
>>Rick
>>--
>>Rick Rankin
>>rrankin AT primenet DOT com
>>
>>> -----Original Message-----
>>> From: Suhaib M. Siddiqi [mailto:Ssiddiqi AT InspirePharm DOT Com]
>>> Sent: Saturday, March 13, 1999 6:01 PM
>>> To: Rick Rankin; cygwin AT sourceware DOT cygnus DOT com
>>> Subject: Re: find, ksh, and job control
>>>
>>>
>>>
>>>
>>>
>>> >> If you are on NT do not include Cygwin to PATH.  Best start Cygwin by
>>> >                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> >Why not? I have it in my path because I want to be able to run cygwin
>>> >commands from bash or from cmd.exe.
>>> >
>>>
>>> I can also run cygwin commands from cmd.exe.  For this purpose, I
created
>>> another batch file, called cygnus-dos.bat and replashed the *bash* with
>>> *cmd*  If I start NT cmd.exe using this my *cygnus-dos.bat* file,
>>> I can use
>>> all of my cygwin commands from cmd.exe prompt, and stll do not get any
>>> conflicts.
>>>
>>>
>>> --SMS
>>>
>>> >Rick
>>> >--
>>> >Rick Rankin
>>> >rrankin AT primenet DOT com
>>> >
>>>
>>
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -