Re: [PATCH v3 04/42] git-completion.bash: introduce __gitcomp_builtin
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Feb 23, 2018, 10:30 UTC
- Message-ID
- <CACsJy8Avto9W_xUJLv+_uQMXLOsXDBz1Bo8kqZNhzs1dKKhb0A@mail.gmail.com>
- In-Reply-To
- <CAM0VKjk17VgGAHr8jJXft4twij61KPLUDYSeHm6TXttksynd8Q@mail.gmail.com>
On Wed, Feb 14, 2018 at 10:35 PM, SZEDER Gábor <szeder.dev@gmail.com> wrote:
Show 17 quoted lines
>> +__gitcomp_builtin () > > Please excuse the bikeshed at v3, but I don't like the name of this > function. It indicates that it completes builtins, but it completes > options of builtins, and even then only the options of those using parse > options. Furthermore, the '__gitcomp' prefix is usually used for > functions that merely put words into COMPREPLY, but this function does a > whole lot more (getting the options from builtins, include and exclude > options, caching). > > Alas I don't have any great name; __git_complete_options is better, > because it uses the right function name prefix, but only slightly > better, because it can't generally be used to complete options, as it > won't work with scripts or with builtins not using parse options (though > with time more scripts will be turned into builtins and more builtins > will use parse options). I'm not sure it's that match better to make it > worth changing fourty-odd patches.
Since it's still on 'pu', renaming is still an option. I don't mind renaming (and I'll need to check every patch anyway when I make --rerere-autoupdate completable). Say "do" and I will.
-- Duy