Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Envelope-To: cygwin AT cygwin DOT com
X-Comment-To: Randall R Schulz
To: Randall R Schulz <rrschulz AT cris DOT com>
Cc: cygwin AT cygwin DOT com
Subject: Re: a problem with search path? (was: Multiple backslashes)
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210144103 DOT 02846b60 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210104242 DOT 02557d60 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210095957 DOT 023d7eb0 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210090253 DOT 00aa0608 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210090253 DOT 00aa0608 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210095957 DOT 023d7eb0 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210104242 DOT 02557d60 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020210144103 DOT 02846b60 AT pop3 DOT cris DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020211082848 DOT 00aa1908 AT pop3 DOT cris DOT com>
From: Dmitry Bely <dbely AT mail DOT ru>
Date: 12 Feb 2002 19:02:54 +0300
In-Reply-To: <5.1.0.14.2.20020211082848.00aa1908@pop3.cris.com>
Message-ID: <bseuzo0h.fsf@mail.ru>
Lines: 45
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service (Windows))
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Randall R Schulz <rrschulz AT cris DOT com> writes:

> Did you read the manual sections I referred you to?

Yes.

> CYGWIN=glob (withour without ":ignorecase") vs. CYGWIN=noglob _only_
> pertains when a non-Cygwin process invokes a Cygwin binary.
> 
> Thus, "CYGWIN=[no]glob" is irrelevant when you're invoking a program
> (either Cygwin or Win32) from BASH (Cygwin).

I realize that. I just used "bash inside bash" example to show that the
problem is inside Cygwin/bash, not in cmd<->cygwin or
CreateProcess()<->cygwin interface.

> You need to reason about what's happening, not try to apply a single
> cookbook formula. At a minimum, you must know how many times globbing
> (and, hence, escaping) will be applied to any given string.

I understand all this (I hope). And then I run

C:\>set CYGWIN=noglob
C:\>bash -c "c:\\cygwin\\bin\\ls.exe"
bash: c:\cygwin\bin\ls.exe: command not found

from cmd.exe, I expect that it should work (if not, could you finally
explain me there I am mistaken in this very case and rewrite it
properly). It does not. But in the same time any of the following works:

C:\>set CYGWIN=noglob
C:\>bash -c "c:/cygwin\\bin\\ls.exe"

C:\>set CYGWIN=noglob
C:\>bash -c "..\\bin\\ls.exe"  (c:\cygwin\bin is in the PATH)

That's why I think that the problem is that Cygwin (or bash) fails to
understand that "c:\\cygwin\\bin\\ls.exe" is the _absolute_ path, and tries
to locate ls using PATH directories. I see relatively long delay and HDD
LED blinking before "command not found" message appears (of course if
search directories are not in the file cache). Don't you think that all
this have nothing to do with globbing?

Hope to hear from you soon,
Dmitry



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/