RE: a problem with search path? (was: Multiple backslashes)

RE: a problem with search path? (was: Multiple backslashes)

[Stephan Mueller]

I'm using Windows XP.
stephan();

-----Original Message-----
From: Dmitry Bely [mailto:dbely@mail.ru] 
Sent: Tuesday, February 12, 2002 8:10 AM
To: Stephan Mueller
Cc: cygwin@cygwin.com
Subject: Re: a problem with search path? (was: Multiple backslashes)


"Stephan Mueller" <smueller@microsoft.com> writes:

> Latest everything.  bash 2.05a.0(2)  Cygwin DLL v 1.3.9-1. stephan();

Just upgraded my installaton - still no success. What OS are you using?
I currenly have Windows 2000 Workstation SP2 (build 2195)

> > >From a bash shell:
> > [~] bash -c "d:\\\\cygwin\\\\bin\\\\ls.exe"
> > 
> > >From cmd.exe
> > [D:\] bash -c "d:\\cygwin\\bin\\ls.exe"
> > 
> > My CYGWIN variable includes glob:ignorecase

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/

Re: a problem with search path? (was: Multiple backslashes)

[Dmitry Bely]

"Stephan Mueller" <smueller@microsoft.com> writes:

> Latest everything.  bash 2.05a.0(2)  Cygwin DLL v 1.3.9-1.
> stephan();

Just upgraded my installaton - still no success. What OS are you using? I
currenly have Windows 2000 Workstation SP2 (build 2195)

> > >From a bash shell:
> > [~] bash -c "d:\\\\cygwin\\\\bin\\\\ls.exe"
> > 
> > >From cmd.exe
> > [D:\] bash -c "d:\\cygwin\\bin\\ls.exe"
> > 
> > My CYGWIN variable includes glob:ignorecase

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/

Re: a problem with search path? (was: Multiple backslashes)

[Dmitry Bely]

Randall R Schulz <rrschulz@cris.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/

RE: a problem with search path? (was: Multiple backslashes)

[Stephan Mueller]

Latest everything.  bash 2.05a.0(2)  Cygwin DLL v 1.3.9-1.
stephan();


-----Original Message-----
From: Dmitry Bely [mailto:dbely@mail.ru] 
Sent: Monday, February 11, 2002 2:38 AM
To: Stephan Mueller
Cc: cygwin@cygwin.com
Subject: Re: a problem with search path? (was: Multiple backslashes)


"Stephan Mueller" <smueller@microsoft.com> writes:

> >From a bash shell:
> [~] bash -c "d:\\\\cygwin\\\\bin\\\\ls.exe"
> 
> >From cmd.exe
> [D:\] bash -c "d:\\cygwin\\bin\\ls.exe"
> 
> My CYGWIN variable includes glob:ignorecase

But it does not work for me even with your settings :-( What is the
version of cygwin and bash that you are using?

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/

Re: a problem with search path? (was: Multiple backslashes)

[Randall R Schulz]

Dmitry,

Did you read the manual sections I referred you to?

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

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.

Randall Schulz
Mountain View, CA USA


At 01:31 2002-02-11, you wrote:
>Randall R Schulz <rrschulz@cris.com> writes:
>
> > I'm trying to help you, but you seem insistent on just declaring
> > Cygwin buggy. It is not and it is possible for you to resolve the
> > problem. I gave you all the information you need to do so.
> >
> > One last time, I'll answer your points...
>
>Randall, of course it's up to you whether to answer or not. Nonetheless, 
>thank you for your comments. For everyone else, I don't claim that cygwin 
>is buggy (although it might be the case). I just trying to understand 
>what's going on and how to solve my very problems. Randall's advice to add 
>CYGWIN=noglob _partially_ solves them (yes, really, it makes 2 BS 
>sufficient then 'bash -c "ls c:\\"' is called via syscall 
>CreateProcess()). But:
>
>How to write the following command with _backslashes_ to make it work? 
>Suppose we launch it from bash:
>
>bash-2.05$ bash -c "ls c:\\\\cygwin\\\\bin\\\\ls.exe"
>c:\cygwin\bin\ls.exe
>bash-2.05$ bash -c "c:\\\\cygwin\\\\bin\\\\ls.exe"
>bash: c:\cygwin\bin\ls.exe: command not found
>bash-2.05$
>
>CYGWIN=noglob does _not_ help.
>
>How many backslahes should I put there? But please check that it _really_ 
>works before answering.
>
>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/

Re: a problem with search path? (was: Multiple backslashes)

[Dmitry Bely]

"Stephan Mueller" <smueller@microsoft.com> writes:

> >From a bash shell:
> [~] bash -c "d:\\\\cygwin\\\\bin\\\\ls.exe"
> 
> >From cmd.exe
> [D:\] bash -c "d:\\cygwin\\bin\\ls.exe"
> 
> My CYGWIN variable includes glob:ignorecase

But it does not work for me even with your settings :-( What is the version
of cygwin and bash that you are using?

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/

RE: a problem with search path? (was: Multiple backslashes)

[Stephan Mueller]

For me, these just worked:

From a bash shell:
[~] bash -c "d:\\\\cygwin\\\\bin\\\\ls.exe"

From cmd.exe
[D:\] bash -c "d:\\cygwin\\bin\\ls.exe"

My CYGWIN variable includes glob:ignorecase

stephan();


-----Original Message-----
From: Dmitry Bely [mailto:dbely@mail.ru] 
Sent: Monday, February 11, 2002 1:31 AM
To: cygwin@cygwin.com
Subject: a problem with search path? (was: Multiple backslashes)


Randall R Schulz <rrschulz@cris.com> writes:

> I'm trying to help you, but you seem insistent on just declaring
> Cygwin buggy. It is not and it is possible for you to resolve the
> problem. I gave you all the information you need to do so.
> 
> One last time, I'll answer your points...

Randall, of course it's up to you whether to answer or not. Nonetheless,
thank you for your comments. For everyone else, I don't claim that
cygwin
is buggy (although it might be the case). I just trying to understand
what's going on and how to solve my very problems. Randall's advice to
add
CYGWIN=noglob _partially_ solves them (yes, really, it makes 2 BS
sufficient then 'bash -c "ls c:\\"' is called via syscall
CreateProcess()). But:

How to write the following command with _backslashes_ to make it work?
Suppose we launch it from bash:

bash-2.05$ bash -c "ls c:\\\\cygwin\\\\bin\\\\ls.exe"
c:\cygwin\bin\ls.exe
bash-2.05$ bash -c "c:\\\\cygwin\\\\bin\\\\ls.exe"
bash: c:\cygwin\bin\ls.exe: command not found
bash-2.05$

CYGWIN=noglob does _not_ help.

How many backslahes should I put there?
But please check that it _really_ works before answering.

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/


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

a problem with search path? (was: Multiple backslashes)

[Dmitry Bely]

Randall R Schulz <rrschulz@cris.com> writes:

> I'm trying to help you, but you seem insistent on just declaring
> Cygwin buggy. It is not and it is possible for you to resolve the
> problem. I gave you all the information you need to do so.
> 
> One last time, I'll answer your points...

Randall, of course it's up to you whether to answer or not. Nonetheless,
thank you for your comments. For everyone else, I don't claim that cygwin
is buggy (although it might be the case). I just trying to understand
what's going on and how to solve my very problems. Randall's advice to add
CYGWIN=noglob _partially_ solves them (yes, really, it makes 2 BS
sufficient then 'bash -c "ls c:\\"' is called via syscall
CreateProcess()). But:

How to write the following command with _backslashes_ to make it work?
Suppose we launch it from bash:

bash-2.05$ bash -c "ls c:\\\\cygwin\\\\bin\\\\ls.exe"
c:\cygwin\bin\ls.exe
bash-2.05$ bash -c "c:\\\\cygwin\\\\bin\\\\ls.exe"
bash: c:\cygwin\bin\ls.exe: command not found
bash-2.05$

CYGWIN=noglob does _not_ help.

How many backslahes should I put there?
But please check that it _really_ works before answering.

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/