Message-ID: <4A72C1FA.7060509@gmail.com>
Date: Fri, 31 Jul 2009 11:05:46 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Forward slashes in path and pipes
References: <h4tnoi$lvr$1@ger.gmane.org> <4A726C93.9090403@gmail.com> <h4tv7c$3gl$1@ger.gmane.org>
In-Reply-To: <h4tv7c$3gl$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Andrew DeFaria wrote:
>> For some reason (the presence of the pipe?) cmd.exe parses the forward
>> slash as an options separator rather than a path component in one case
>> but not the other. Quoting removes the ambiguity.
> Yes, my Cygwin question would be why does it store "/" in the registry
> for what is obviously a Windows path?

  Because that is a correct and valid syntax for a windows path.  Just because
cmd.exe can misparse it when you fail to quote it doesn't change that; it's no
more an "invalid" or "non-Windows" path than one with a space in it, which will
also give cmd.exe problems if you fail to quote it.

    cheers,
      DaveK


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