This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Possible bug: SH failure when calling command.com
- To: "Arthur I Schwarz" <Arthur_I_Schwarz at West dot Raytheon dot com>,<cygwin at cygwin dot com>
- Subject: RE: Possible bug: SH failure when calling command.com
- From: "Ronald Landheer" <info at rlsystems dot net>
- Date: Wed, 19 Sep 2001 21:09:11 +0200
Hello Arthur,
That's not what I'm after: I'm after the reason sh crashes when I start
the Windoze command.com shell. I don't care much for substituting Cygwin
stuff for Windoze stuff: I like Cygwin better. The only thing is that
there was a rather lively discussion on the subject recently, which
prompted me to try this - which made me find the crash problem.
It is easily reproducible (it happens every time), so it must be
debuggable.. (I just thought someone might already have done some of the
work..)
Greetz!
Ronald
> -----Original Message-----
> From: Arthur I Schwarz [mailto:Arthur_I_Schwarz@West.Raytheon.com]
> Sent: Wednesday, September 19, 2001 5:52 PM
> To: Ronald Landheer
> Subject: Re: Possible bug: SH failure when calling command.com
>
>
>
>
> Don't know if this is what you want, but include the path to the location
> of the WinDOZ commands in PATH. Reference the WinDOZ 'dir' command as DIR.
> The same applies to all the remaining windows commands,
> capitilize them and
> then they are distinguished from the Cygwin look-a-likes.
>
> art
>
>
>
> Sent by: cygwin-owner@sources.redhat.com
>
>
> To: <cygwin@cygwin.com>
> cc:
>
> Subject: Possible bug: SH failure when calling command.com
>
> Hello all,
>
> Prompted by a recent thread on this list, I decided to make a dir
> wrapper which calls the command line interpreter of Windoze and executes
> a proper dir command. The script looks like this:
>
>
>
>
>
--
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/