This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: "start" for Cygwin
- From: Charles Wilson <cwilson at ece dot gatech dot edu>
- To: Robert Collins <robert dot collins at itdomain dot com dot au>
- Cc: Michael Schaap <cygwin at mscha dot org>, cygwin at cygwin dot com
- Date: Sun, 03 Mar 2002 01:16:09 -0500
- Subject: Re: "start" for Cygwin
- References: <FC169E059D1A0442A04C40F86D9BA76008AAF9@itdomain003.itdomain.net.au>
Ah -- and that explains why one previously had to do "cmd /c start foo"
from a bash shell. Okay, according to my tests (I put a 'start' shell
script in my /usr/bin directory.) From bash, 'start foo' causes my
script to run. From cmd, 'start foo' causes the builtin cmd command to
run (even tho D:/cygwin/bin is in the front of my PATH).
This is good -- I withdraw my objection (such as it was).
Anybody else think this is a good cygutil? I think it *probably* is...
--Chuck
Robert Collins wrote:
> Start is a cmd builtin - there is no start.exe
>
> Rob
>
>
>
>
>>-----Original Message-----
>>From: Charles Wilson [mailto:cwilson@ece.gatech.edu]
>>
> Anyway, I personally have no objection to including start in cygutils --
>
> but the sudden appearance of a 'start.exe' command in /usr/bin (which
> could hide WINNT/start.exe) may cause consternation in some quarters.
>
> FYI, I've just completed the following HOW-TO-CONTRIBUTE (to cygutils)
> document. It will show up in /usr/doc/cygutils-X.Y.Z/ in the next
> release of cygutils.
>
> --Chuck
>
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/