Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.1.0.14.2.20020925101421.01fc6870@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Wed, 25 Sep 2002 10:22:40 -0700
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	RE: cygpath returns garbage if DOS/win2k input environment
	variable is too long?
In-Reply-To:	<KJEOKFJJEDMIGBEEJCHCMEBHNDAA.ralfhauser@gmx.ch>
References:	<20020925164428 DOT 83889 DOT qmail AT web20006 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0

Ralf,

In addition to the need to use "-p" in this case (which I mentioned 
earlier--you did see that message, didn't you?), you should quote your 
$CLASSPATH variable reference.

You might want to scrutinize you scripts to make sure they're 
"space-tolerant." Many Unix-land scripts are written under the assumption 
that there are no characters in variable names and arguments that are 
special to the shell that interprets that script. Under Windows, this is 
often a bad assumption and a space is the most common (but by no means the 
only) character that violates that assumption.

Note that it's not easy for "cygpath" to issue errors when you misuse it, 
since anything you pass in can be converted between Unix and Windows or DOS 
formats. But if you ask it to perform the wrong conversion, you shouldn't 
expect the right result. About the only diagnostic it could provide would 
be for the use of characters that are forbidden in Windows file names (\, 
/, :, *, ?, <, >, |).


Randall Schulz
Mountain View, CA USA


At 09:55 2002-09-25, Ralf Hauser wrote:
>Thx! Unfortunately still only the same garbage in the mylog file.
>Apparently, no warning goes to stderr?
>
> > -----Original Message-----
> > From: Joshua Daniel Franklin [mailto:joshuadfranklin AT yahoo DOT com],
>cygwin AT cygwin DOT com
> > Sent: Mittwoch, 25. September 2002 18:44
> > --- Ralf Hauser <ralfhauser AT gmx DOT ch> wrote:
> > > 1) is there a way to see an error-message from cygpath (a log
> > file or some
> > > way to see stderr if there is any of that)?
> > > 2) I did a work-around with assembling the path again in my
> > .tcshrc. This is
> > > not convenient. Any better ideas...?
> >
> > My only thought is to wrap the cygpath command in a shell script:
> >
> > cygpath --unix $CLASSPATH 2>&1 >>mylog
> >
> > cygpath uses the MAXPATH (1024 for win9x??)


--
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/

- Raw text -