This is the mail archive of the
mailing list for the Cygwin project.
RE: cygpath returns garbage if DOS/win2k input environment variable is too long?
- From: Joshua Daniel Franklin <joshuadfranklin at yahoo dot com>
- To: hauser at acm dot org
- Cc: cygwin at cygwin dot com
- Date: Wed, 25 Sep 2002 17:54:04 -0700 (PDT)
- Subject: RE: cygpath returns garbage if DOS/win2k input environment variable is too long?
Looks like you'll have to take Chris' advice and at least look at the
cygpath source. Does it work with a shorter CLASSPATH?
Oh, and follow Randy's advice about the --path option, too.
--- Ralf Hauser <firstname.lastname@example.org> 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:email@example.com],
> > Sent: Mittwoch, 25. September 2002 18:44
> > --- Ralf Hauser <firstname.lastname@example.org> 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??)
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html