X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 2 Feb 2011 12:01:14 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: bad PATH conversion under XP
Message-ID: <20110202110114.GB2675@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4D3F6779 DOT 5010100 AT laposte DOT net> <4D3F8295 DOT 2020109 AT cpan DOT org> <4D488C09 DOT 7050606 AT laposte DOT net> <20110202100409 DOT GB32233 AT calimero DOT vinschen DOT de> <4D4937F5 DOT 7010104 AT gmx DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4D4937F5.7010104@gmx.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Feb  2 11:54, Matthias Andree wrote:
> Am 02.02.2011 11:04, schrieb Corinna Vinschen:
> > On Feb  1 23:41, Cyrille Lefevre wrote:
> >> I'm reporting a cygwin bug...
> >> of course I know I could edit the windows environment variables.
> >> however, this problem has to be fixed.
> > 
> > I agree.  It's not the user's fault that Windows applications and
> > Windows itself add paths to the environment using quotes and trailing
> > backslashes.  I applied a patch which removes those, but only when
> > Cygwin actually fetches the Win32 environment and initially converts the
> > path lists like %Path%.  This is not done when calling the
> > cygwin_conv_path_list function from the application.
> 
> No offense intended, but is it useful to introduce such distinctions as
> to when/where/how the variable is fetched?  It might cause hard-to-debug
> problems later on, don't you think?

Existing applications might rely on the existing behaviour, especially
related to the backslash.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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