From: Charles Wilson <cwilson@ece.gatech.edu>
To: Robert Collins <robert.collins@itdomain.com.au>
Cc: Michael Schaap <cygwin@mscha.org>, cygwin@cygwin.com
Subject: Re: "start" for Cygwin
Date: Sat, 02 Mar 2002 22:16:00 -0000 [thread overview]
Message-ID: <3C81BFA9.2020606@ece.gatech.edu> (raw)
In-Reply-To: <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/
next prev parent reply other threads:[~2002-03-03 6:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-02 22:04 Robert Collins
2002-03-02 22:16 ` Charles Wilson [this message]
2002-03-03 10:08 ` Max Bowsher
-- strict thread matches above, loose matches on Subject: below --
2002-03-04 7:17 Roth, Kevin P.
2002-03-03 3:53 Robert Collins
2002-03-03 3:58 ` David Starks-Browning
2002-03-03 6:07 ` Michael Schaap
2002-03-02 22:22 Stephan Mueller
2002-03-03 0:46 ` Dr. Carsten Bormann
2002-03-03 5:57 ` Michael Schaap
2002-03-03 14:46 ` Dr. Carsten Bormann
2002-03-03 1:31 ` David Starks-Browning
2002-03-02 14:12 Michael Schaap
2002-03-02 21:15 ` Charles Wilson
2002-03-03 5:50 ` Michael Schaap
2002-03-03 14:53 ` Scott Evans
2002-03-13 0:11 ` Charles Wilson
2002-03-13 4:35 ` Michael Schaap
2002-03-14 21:21 ` Michael Schaap
2002-03-16 0:26 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C81BFA9.2020606@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=cygwin@mscha.org \
--cc=robert.collins@itdomain.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).