Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	"Roger Vaughn" <rvaughn AT seaconinc DOT com>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	RE: Cygwin 1.0 "issues"
Date:	Thu, 28 Oct 1999 11:34:49 -0400
Message-ID:	<NDBBKDNNBCDFDHCBEPNGGEPGCAAA.rvaughn@seaconinc.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
In-reply-to:	<19991026220919.C3136@cygnus.com>

Chris, thanks.

> -----Original Message-----
> From: cygwin-owner AT sourceware DOT cygnus DOT com
> [mailto:cygwin-owner AT sourceware DOT cygnus DOT com]On Behalf Of Chris Faylor
>
> On Tue, Oct 26, 1999 at 08:54:35PM -0400, Roger Vaughn wrote:
> >> On Tue, Oct 26, 1999 at 03:48:49PM -0400, Roger Vaughn wrote:
>
> Ok.  The tcsh on the CD was pretty much a straight port.  We didn't go
> out of our way to make it understand MS-DOS paths.  It wasn't a goal for
> any of the utilties that we ported.
>...
> Cygwin *can* use Windows-style paths.  Didn't you just admit this?
>
> If you mean that some utilities, like tcsh, can't handle them, then, of
> course, you're right.  There's not much we can do about that.  We
> certainly don't have the staff to start a crusade of modifying every
> application to understand the c:\ path specifications.  In fact, one of
> the early goals of cygwin was to create a layer which avoids this to
> make porting the GNU tools easier.

Ok, I can see that I'm going to have to come up with some concrete cases for
you to look at.

Yes, Cygwin does accept Win-style paths - sometimes.  Or perhaps I'm having
trouble with the way Cygwin insists on rewriting the paths into its style -
which means they cannot be used by my native utils.

But you see, this is exactly my point.  Cygnus didn't spent much time on
tcsh or the other contrib stuff - nor do I expect you to be able to.
Business is business and cygwin isn't a cash cow for you.  So this means I
have to rely on ports from a variety of sources, which means I have to get
them working together.

With b20, everything worked together beautifully.  But the path handling has
obviously changed in 1.0, and now I'm having fits trying to get my tools to
work together.  I was much happier when Cygwin didn't try as hard to emulate
UNIX paths.  (Yes, I understand the motivation for it though.)

If I'm the only person having this much trouble with it, though, then I
suppose I'll just have to work it out for myself.

Thanks,

rog



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

- Raw text -