X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 10 Mar 2010 10:09:41 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: allow executing a path in backslash notation Message-ID: <20100310150941.GB19509@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <720660 DOT 16774 DOT qm AT web88302 DOT mail DOT re4 DOT yahoo DOT com> <20100310092536 DOT GS6505 AT calimero DOT vinschen DOT de> <4B9775C2 DOT 8000300 AT towo DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Wed, Mar 10, 2010 at 11:59:33AM +0100, Ilya Beylin wrote: >Thomas, you are right, it is rather an issue with bash: >when does not see a slash in the command name, it starts path >searching, and of course finds nothing. >Looks like a bug. > >$ "$WINDIR\system32\cmd.exe" /c echo ok >bash: C:\WINDOWS\system32\cmd.exe: command not found > >$ "$WINDIR/system32\cmd.exe" /c echo ok >ok You are apparently missing the point of Cygwin. It was developed to allow porting of things like bash with little or no patching. It was for this reason that the UNIX path translation layer was developed. I understand that you and others may think it is vitally important that things like MS-DOS paths are handled perfectly but it is definitely not a goal for this project. It is not a bug when bash or some other tool doesn't work perfectly with MS-DOS paths. cgf -- 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