RE: 1.5.25-7: problem about bash completion

2008-01-09 Thread Dave Korn
On 09 January 2008 14:00, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to kou yu on 12/26/2007 10:07 AM: >>> POSIX *allows* '//something' to have a special meaning. It doesn't >>> state that it is necessarily the syntax for SMB share paths. >>> >> In fact, i

Re: 1.5.25-7: problem about bash completion

2008-01-09 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to kou yu on 12/26/2007 10:07 AM: |> POSIX *allows* '//something' to have a special meaning. It doesn't |> state that it is necessarily the syntax for SMB share paths. |> | In fact, if you simply say that this is not a bug of cygwin, but a

Re: 1.5.25-7: problem about bash completion

2007-12-26 Thread kou yu
On Dec 23, 2007 1:26 PM, Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Sun, Dec 23, 2007 at 01:02:23PM +0800, kou yu wrote: > >o, maybe you are right. > > It's a good bet that she is. > > >But I am a little confused. "//server/share" is the POSIX syntax for > >SMB share paths, but on windows t

Re: 1.5.25-7: problem about bash completion

2007-12-22 Thread Christopher Faylor
On Sun, Dec 23, 2007 at 01:02:23PM +0800, kou yu wrote: >o, maybe you are right. It's a good bet that she is. >But I am a little confused. "//server/share" is the POSIX syntax for >SMB share paths, but on windows the syntax is "\\server\share". POSIX *allows* '//something' to have a special mean

Re: 1.5.25-7: problem about bash completion

2007-12-22 Thread kou yu
o, maybe you are right. But I am a little confused. "//server/share" is the POSIX syntax for SMB share paths, but on windows the syntax is "\\server\share". And why on linux I input "cd //usr/", the completion would not become slow, i.e. why on linux, the syntax "//xxx/xxx" would not be considered

Re: 1.5.25-7: problem about bash completion

2007-12-22 Thread Corinna Vinschen
On Dec 22 17:43, kou yu wrote: > If I input: > cmdname /dirname/ > then I get the normal completion output immediately. > > But if I input: > cmdname //dirname/ > then I must wait for a long time for those completion output. And the > terminal seems to be frozen, have not a single response