Re: Zsh filename completion sluggishness?

[Christopher Faylor <cgf at redhat dot com>]

On Fri, Feb 14, 2003 at 11:38:06AM -0700, Matt Armstrong wrote:
>Christopher Faylor <cgf-cygwin@cygwin.com> writes:
>
>> On Fri, Feb 14, 2003 at 10:12:54AM -0700, Matt Armstrong wrote:
>>>In the Win32 world, quotes around path elements are valid.  If I have:
>>>
>>>    PATH="c:\foo bar"
>>>
>>>cmd.exe will find executables in that dir.
>>>
>>>When I run bash or zsh, things in "c:\foo bar" aren't found.
>>
>> This is a UNIX emulation environment.  "c:\foo bar" doesn't mean the c drive
>> in a PATH variable.  It means the 'c' directory followed by the '\foo bar'
>> directory.  Colon is the separator for PATH.
>>
>> The correct syntax for the above is PATH="/cygdrive/c/foo bar" .
>
>I understand completely -- as I said somewhat ambiguously I was
>setting the path to "c:\foo bar" in cmd.exe, then running bash.
>
>When Cygwin initializes its PATH from the Win32 one, it doesn't handle
>quoted elements properly.
>
>E.g. cygwin converts the Win32 path like this:
>
>    c:\foo;"c:\bar" -> /cygdrive/c/foo:"c:\bar"
>
>But it should do this:
>
>    c:\foo;"c:\bar" -> /cygdrive/c/foo:/cygdrive/c/bar

Ah, sorry.  I see what you're saying now.

Yes, that's "arguably" a bug.

cgf

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