X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-ASG-Debug-ID: 1283449539-589e30d10001-w5GHUG
X-Barracuda-Envelope-From: daniel AT fgm DOT com
X-Barracuda-Apparent-Source-IP: 216.2.55.102
X-ASG-Whitelist: Client
Message-ID: <4C7FE2C2.8060104@fgm.com>
Date: Thu, 2 Sep 2010 13:45:38 -0400
From: Daniel Barclay <daniel AT fgm DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6
MIME-Version: 1.0
To: <cygwin AT cygwin DOT com>
Subject: Windows-style pathname does not work as command - why?
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
X-ASG-Orig-Subj: Windows-style pathname does not work as command - why?
Content-Transfer-Encoding: 7bit
X-Barracuda-Connect: UNKNOWN[216.2.55.102]
X-Barracuda-Start-Time: 1283449539
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://spam.fgm.com:8000/cgi-mod/mark.cgi
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

I don't quite understand this behavior:

$ ls C:\\tools\\emacs-23.2\\bin\\runemacs.exe
C:\tools\emacs-23.2\bin\runemacs.exe
$ C:\\tools\\emacs-23.2\\bin\\runemacs.exe
bash: C:\tools\emacs-23.2\bin\runemacs.exe: command not found

In particular, why is it that bash does not understand that Windows
pathname when it is used as a command argument, even though bash and
Cygwin clearly understand it when it is used as a command argument?


Is that behavior a bug (e.g., does bash try to judge whether the command
is an absolute vs. relative pathname without either first converting to
a Unix-style pathname or otherwise recognizing Windows-style pathname)?

Or is it some known irregularity (resulting from trying to handle both
Windows- and Unix-style pathnames) that couldn't be resolved?

Thanks,
Daniel




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