-----BEGIN PGP SIGNED MESSAGE-----
Il 30/01/2013 19:55, Marc Khouzam ha scritto:
>>>> The new logic in git-completion.bash tells bash that 'filenames'
>>>> completion is ongoing so bash will add a '/' after directories.
>>>> Sadly, tcsh won't do that, so it would be simpler if
>>>> git-completion.bash added the '/' itself. I looked at the
>>>> git-completion.bash script changes and I noticed that for
>>>> bash version < 4, you have to add the '/' yourself.
> The compatible version is not only required for Bash; you can
> use it for
> other shells.
> Try to redefine the __git_index_file_list_filter function to use the
> version that adds a slash to directory names.
>> I hadn't thought of that!
>> Although I would prefer not to have special cases like that,
>> it does work well.
The zsh compatible code does something like this; this is the reason I
tried to do the same thing, in order to keep coding consistent.
> Bash 4.1.5(1) always adds an additional slash for directories.
> I have tested it right now: change the filter function to use the
> compatible version:
> __git_index_file_list_filter ()
> # Default to Bash >= 4.x
> Then running `git add <TAB>` inside the git repository, I get
> this file
> completion list:
> $ git add <TAB>
>> Ok, I see. The double-slash is visible in the completion list
>> but it does not appear on the command-line when bash automatically
>> adds it.
Right; that's why I wrote in the comment that Bash behaviour "seems" stupid.
But probably that comment should be remove or changed for the final
version of the patch; I'll leave that to a Bash expert.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html