I'm using Windows XP.
stephan();
-Original Message-
From: Dmitry Bely [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 8:10 AM
To: Stephan Mueller
Cc: [EMAIL PROTECTED]
Subject: Re: a problem with search path? (was: Multiple backslashes)
"Stephan Mueller" &l
"Stephan Mueller" <[EMAIL PROTECTED]> 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:\\
Randall R Schulz <[EMAIL PROTECTED]> 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 inv
"Robinow, David" <[EMAIL PROTECTED]> writes:
> Have you looked into the use of the XEmacs variable setq directory-sep-char?
Hmm, it might really be the solution. Thank you very much for the idea.
Hope to hear from you soon,
Dmitry
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
"Stephan Mueller" <[EMAIL PROTECTED]> writes:
> >From a bash shell:
> [~] bash -c "d:cygwinbinls.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 vers
PROTECTED]]
Sent: Monday, February 11, 2002 1:31 AM
To: [EMAIL PROTECTED]
Subject: a problem with search path? (was: Multiple backslashes)
Randall R Schulz <[EMAIL PROTECTED]> writes:
> I'm trying to help you, but you seem insistent on just declaring
> Cygwin buggy. It is no
Randall R Schulz <[EMAIL PROTECTED]> 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,
Dmitry,
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...
At 11:46 2002-02-10, you wrote:
>Randall R Schulz <[
Randall R Schulz <[EMAIL PROTECTED]> writes:
> If your XEmacs is a Windows app and not a Cygwin one, then my caveats
> apply because it is another example of a Windows process initiating a
> Cygwin program.
It's not acceptable? How then to invoke the bash itself :-)
> From the Cygwin FAQ:
> -=
Dmitry,
If your XEmacs is a Windows app and not a Cygwin one, then my caveats apply
because it is another example of a Windows process initiating a Cygwin program.
From the Cygwin FAQ:
-==-
How does wildcarding (globbing) work?
If the DLL thinks it was invoked from a DOS style prompt, it runs
Randall R Schulz <[EMAIL PROTECTED]> writes:
> What I said is accurate. However, in the absence of any explicit
> mention on your part, I assumed you were issuing the commands you
> specified from a Cygwin shell. It now appears you are entering them
> into CMD.exe.
>
> If I'm not mistaken, argum
Dmitry,
What I said is accurate. However, in the absence of any explicit mention on
your part, I assumed you were issuing the commands you specified from a
Cygwin shell. It now appears you are entering them into CMD.exe.
If I'm not mistaken, arguments are processed differently in Cygwin binari
Randall R Schulz <[EMAIL PROTECTED]> writes:
> Apart from the fact that this question involves Windows native path
> name syntax (which, by the way, works equally well with forward
> slashes), this is not Cygwin-specific.
>
>
> There are two levels or rounds of interpretation of your command
>
Dmitry,
Apart from the fact that this question involves Windows native path name
syntax (which, by the way, works equally well with forward slashes), this
is not Cygwin-specific.
There are two levels or rounds of interpretation of your command string.
The first is applied by the shell that in
This is probably a FAQ, but can you explain me why
bash -c "ls c:"
requires 4 backslashes? I can understand why 2 BS is needed, but 4 BS IMHO
are too much :-)
Hope to hear from you soon,
Dmitry
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http
15 matches
Mail list logo
