X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 29 Mar 2010 19:16:21 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: allow executing a path in backslash notation Message-ID: <20100329171621.GS18364@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <847981.91314.qm@web88305.mail.re4.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <847981.91314.qm@web88305.mail.re4.yahoo.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 16 09:15, Ilguiz Latypov wrote: > > > I checked this situation in cmd.exe, and it is not capable of using > > paths relativ to %Path%. In other words, if %Path% contains a path > > c:\foo and you have two files C:\foo\baz.exe and C:\foo\bar\baz.exe, > > then calling "baz" works, but calling "bar\baz" fails. > > I only meant resolving relative commands against the current directory. That is, regardless of %PATH%, bar\baz is allowed to resolve if the current directory is c:\foo. > > The absolute paths are already resolved. > > My patch allows relative and absolute commands in backslash notation, as the test case shows. > > > So, yes, maybe we should care for this situation but it's not something > > to worry about a lot. I'll look into it again at some point after 1.7.2 > > has been released. > > Thanks. This should be fixed in CVS now and will be in 1.7.3. 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