From: Manlio Perillo Date: Tue, 08 Jan 2013 17:54:09 GMT Subject: Re: [PATCH v4] git-completion.bash: add support for path completion Message-ID: <50EC5D41.6030209@gmail.com> In-Reply-To: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 05/01/2013 21:23, Marc Khouzam ha scritto: > [...] > 4- Completion choices include their entire path, which is not what bash does by default. For example: >> cd git/contrib >> ls completion/git- > git-completion.bash git-completion.tcsh git-completion.zsh git-prompt.sh > but >> git rm completion/git- > completion/git-completion.bash completion/git-completion.tcsh completion/git-completion.zsh completion/git-prompt.sh > notice the extra 'completion/' before each completion. This can get pretty large when completing with > many directory prefixes. The current tcsh completion has the same problem which I couldn't fix. However, I am > not sure if it can be fixed for bash. > > I personally don't think this is regression, just an slight annoyance. > After some searching, I found how this is supposed to be done. It is possible to use the -o filenames option to tell Bash completion that "the compspec generates filenames, so it can perform any filename-specific processing". Unfortunately this option must be passed to the complete builtin command, and we can not do this, since the comspec not always contains filenames. > [...] Regards Manlio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDsXUEACgkQscQJ24LbaURMlgCdEyeSRTRktKtGuDxq4HX1meWt IV4AmwS6wasCip+1u4vS2FwG8AlXXB7r =pN8F -----END PGP SIGNATURE-----