Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID:	<435C2A4A.C4D58EA5@dessent.net>
Date:	Sun, 23 Oct 2005 17:26:50 -0700
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: When are Windows Short Path Names required
References:	<gf4ll19t24s5el791n26rudlum24i066ot AT 4ax DOT com> <lebnl1thgfncfg24fmc959nm75o9jtcpp7 AT 4ax DOT com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

zzapper wrote:

> >I've just had another case where the I had to use the short form, is the short form the "real name"?
> I think I've may be mislead you, I think my problem was more that when theres an interaction between
> *nix scripts & environment. Sometimes even quoting doesn't seem to carry the correct path info thru
> to the final WinApp , so you have to move the app to non-space path location or use the short name
> above.

Sometimes it can be hard, especially when you are dealing with both
Cygwin and non-Cygwin programs, because the quoting rules differ.  But
it is always possible, and I can't believe that there exists a situation
where you are actually forced to use the short filename.  If you have
one, post it.

Brian

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

- Raw text -