X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40 X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4B9775C2.8000300@towo.net> 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> Date: Wed, 10 Mar 2010 11:59:33 +0100 Message-ID: Subject: Re: allow executing a path in backslash notation From: Ilya Beylin To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 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 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 -- Ilya -- 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