RE: 1.5.25-7: problem about bash completion
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, if you simply say that this is not a bug of cygwin, but a feature, then I would believe you. It is a feature of cygwin that // is used, in accordance with SUSv3 and POSIX, as the implementation-defined start for remote paths. It is a feature of Linux that // is treated as an implementation-defined synonym of /. It's not just that: it's definitely a bug in applications when they blindly append paths without caring if they double up slashes or not, just because it /usually/ works. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25-7: problem about bash completion
-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 | feature, then I would believe you. It is a feature of cygwin that // is used, in accordance with SUSv3 and POSIX, as the implementation-defined start for remote paths. It is a feature of Linux that // is treated as an implementation-defined synonym of /. Live with it. Bash completion will always take its time when completing on // because it requires a network access, rather than a local hard drive search of /, and there is nothing I can or want to do about it. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] volunteer cygwin bash maintainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhNNJ84KuGfSFAYARAn2oAKCE5rG7m0KX9If3dAAOJLqBWlFmmQCggFZn g+fesohKPKCDi/kvirpXp4I= =YCQ0 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25-7: problem about bash completion
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 the syntax is \\server\share. POSIX *allows* '//something' to have a special meaning. It doesn't state that it is necessarily the syntax for SMB share paths. And why on linux I input cd //usr/tab, the completion would not become slow, i.e. why on linux, the syntax //xxx/xxx would not be considered as remote SMB share. (except smbclient //server/share) Because a '//' has no special meaning on linux. Both '//server/share' and '\\server\share' are valid syntax for Windows. You can believe this or not but Cygwin's behavior is not going to change. In fact, if you simply say that this is not a bug of cygwin, but a feature, then I would believe you. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
1.5.25-7: problem about bash completion
If I input: cmdname /dirname/tab then I get the normal completion output immediately. But if I input: cmdname //dirname/tab then I must wait for a long time for those completion output. And the terminal seems to be frozen, have not a single response. So, is this a bug of cygwin or bash on cygwin? Because my gentoo doesn't have this problem. cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25-7: problem about bash completion
On Dec 22 17:43, kou yu wrote: If I input: cmdname /dirname/tab then I get the normal completion output immediately. But if I input: cmdname //dirname/tab then I must wait for a long time for those completion output. And the terminal seems to be frozen, have not a single response. So, is this a bug of cygwin or bash on cygwin? Because my gentoo doesn't have this problem. This is Windows, not Linux. //server/share is the Windows syntax for remote SMB share paths. This feature is backed by the POSIX standard. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25-7: problem about bash completion
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/tab, the completion would not become slow, i.e. why on linux, the syntax //xxx/xxx would not be considered as remote SMB share. (except smbclient //server/share) On Dec 22, 2007 5:57 PM, Corinna Vinschen [EMAIL PROTECTED] wrote: On Dec 22 17:43, kou yu wrote: If I input: cmdname /dirname/tab then I get the normal completion output immediately. But if I input: cmdname //dirname/tab then I must wait for a long time for those completion output. And the terminal seems to be frozen, have not a single response. So, is this a bug of cygwin or bash on cygwin? Because my gentoo doesn't have this problem. This is Windows, not Linux. //server/share is the Windows syntax for remote SMB share paths. This feature is backed by the POSIX standard. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25-7: problem about bash completion
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 meaning. It doesn't state that it is necessarily the syntax for SMB share paths. And why on linux I input cd //usr/tab, the completion would not become slow, i.e. why on linux, the syntax //xxx/xxx would not be considered as remote SMB share. (except smbclient //server/share) Because a '//' has no special meaning on linux. Both '//server/share' and '\\server\share' are valid syntax for Windows. You can believe this or not but Cygwin's behavior is not going to change. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
