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:	<4F055774D458D51195BC000347246B39E80395@xcguk001.inri.co.uk>
From:	"Watts, Simon (UK)" <swatts AT northgrum-it DOT eu DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: cygpath -s behaviour
Date:	Fri, 6 Sep 2002 15:12:11 +0100
MIME-Version:	1.0

Hello, 

Version information is as follows (pretty recent AFAIK)...

Windows NT 4.0 /sp6

cygpath version 1.21
cygwin 1.3.12-2 (CVS: cygwin-1-3-12-1)

Testing (bash 2.05a.0(3)) (prompt='#')...
<cut>
#
# cygpath -ws long_name_doesnt_exist

#
#
# cygpath -ms long_name_doesnt_exist || echo FAIL

# cygpath -ms long_name_doesnt_exist && echo FAIL

FAIL
#
</cut>

Cygpath does not appear to be writing to stderr, or exiting 
with an error code.

Since I am using a wrapper (shell) function to cygpath anyway, 
I have put a check in there.  I am also ensuring that I am only
passing existing dirs structures (it would be an error in my 
script to have passed the to-be filename, since it could then 
have been constructed with a mangled name rather than the 
correct long form!).


Cheers,


Si.

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