Re: [PATCH 00/11] completion: general cleanups
- From
Manlio Perillo <manlio.perillo@gmail.com>
- Date
- Apr 27, 2013, 20:13 UTC
- Message-ID
- <517C315B.2080106@gmail.com>
- In-Reply-To
- <CAMP44s32WrnFr9Lp03Wu8gC6=FaACBtDbi1rnu=bo94Aa73TBA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Il 27/04/2013 21:15, Felipe Contreras ha scritto:
Show 26 quoted lines
> [...]
>>> @@ -480,7 +481,7 @@ __git_complete_revlist_file ()
>>> # The exception is --committable, which finds the files appropriate commit.
>>> __git_complete_index_file ()
>>> {
>>> - local pfx="" cur_="$cur"
>>> + local pfx="" cur_="$cur" old
>>>
>>> case "$cur_" in
>>> ?*/*)
>>> @@ -490,7 +491,8 @@ __git_complete_index_file ()
>>> ;;
>>> esac
>>>
>>> - __gitcomp_nl "$(__git_index_files "$1" "$pfx")" "$pfx" "$cur_" ""
>>> + compopt -o filenames +o nospace 2> /dev/null || old=1
>>> + __gitcomp_nl "$(__git_index_files "$1" "$pfx" "$old")" "$pfx" "$cur_" ""
>>> }
>>>
>>> __git_complete_file ()
>>>
>>
>> I like the idea (but I have not tested it), however compopt is called
>> two times, for each completion.
>
> Why two times?Ah, right; sorry. I missed the fact that you are using __gitcomp_nl instead of my __gitcomp_file.
Show 9 quoted lines
> >> Maybe we can test for `-o filenames` support when script is loaded, >> where currently there is a Bash version check, and set a global variable? > > Yeah, that's the way bash-completion used to do it. But I wonder if we > should be worrying about this at this point, even bash-completion > dropped support for bash < 4 more than two years ago, and even debian > stable is at 4.1. >
I'm +0.
> [...]
Regards Manlio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlF8MVsACgkQscQJ24LbaUSY/wCgkq8CQeVGNpZFtchiLAKXYpxS wsAAnR0abrQzA1jW+Do7CSuJOZVMRuJu =zPgk -----END PGP SIGNATURE-----