This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.5.25-7: problem about bash completion
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com, ckyoog at gmail dot com
- Date: Wed, 09 Jan 2008 06:59:37 -0700
- Subject: Re: 1.5.25-7: problem about bash completion
- References: <ee03a2470712220143t782852a3w60fd8b9d8e51e4bc@mail.gmail.com> <20071222095758.GC29568@calimero.vinschen.de> <ee03a2470712222102pc7b85e9m9c4f308c0568bceb@mail.gmail.com> <20071223052601.GA23767@ednor.casa.cgf.cx> <ee03a2470712260907n429c5dc7q16b239206a29ce78@mail.gmail.com>
-----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 ebb9@byu.net
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/