X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=BAYES_00,TW_YG
X-Spam-Check-By:	sourceware.org
From:	Gary <cygwin AT garydjones DOT name>
To:	cygwin AT cygwin DOT com
Subject:	cygcheck behaviour when input is not a path
Mail-Followup-To:	cygwin AT cygwin DOT com
Date:	Sat, 29 May 2010 10:09:26 +0200
Message-ID:	<83d3wff7t5.fsf@garydjones.name>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/23.2 (cygwin)
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

How should cygcheck behave when given a "PATH list" (e.g.,
'/bin:/usr/bin'), *without* the -p option?

For example:
$ cygpath -a -p -C ANSI -w /bin:/usr/bin
C:\cygwin\bin;C:\cygwin\bin

= okay. What I expect from RTFMP.

$ cygpath -a -C ANSI -w /bin:/usr/bin
C:\cygwin\bin?\usr\bin

Urk! I would have hoped it wouldn't try to convert this, or at the very
least not the last part, but I don't know if it's a bug, "by design", or
what.

Basically what I am trying to work out is how trustworthy cygpath is
when it receives input that isn't actually a path (for example when it
receives output from a program, some of which might be paths and some of
which might not be).

-- 
Gary
Non-kook (allegedly)

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -