This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [1.7] Undocumented change in accessing by dos drive letters?

Eric Blake wrote:
> Hash: SHA1
> According to aputerguy on 11/5/2009 2:34 PM:
>> >From the cygwin shell, I can do tab-completion on drive letters to get
>> things like C:/usr/bin/ls
>> However, when I press return, I get:
>>       bash: C:/usr/bin/ls: No such file or directory
>> Which is understandable since the file is in C:\cygwin\usr\bin\ls
>> So, why is bash tab completion messing up here? (note the same behavior was
>> true in cygwin 1.5 too so this is not a "new" bug.
> This is not a bug, but a feature of bash tab-completion.  'man bash', and
> search for COMP_WORDBREAKS.  Note that : is a special character, in that
> it marks a boundary of a word (so you are completing "/usr/bin/ls", not
> "c:/usr/bin/ls").  In other words, completion sees a different file name
> than ls.  All the more reason to use posix-y paths and avoid drive letters.

  Or escape the colon -

> admin@ubik ~
> $ c\:/WINNT/system32/[TAB][TAB]
> Display all 1869 possibilities? (y or n)


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]