> > OK how about some thing like this fixup patch? __gitcomp_builtin now
> > allows to add extra options as well as remove some.
> >
> > -- 8< --
> > __gitcomp_builtin ()
> > {
> > + local incl="$2"
> > + local excl="$3"
> > + options="$(__git ${cmd/_/ } --git-completio
On Mon, Feb 5, 2018 at 4:56 AM, Duy Nguyen wrote:
> On Thu, Feb 01, 2018 at 02:16:46PM -0500, Eric Sunshine wrote:
>> On Thu, Feb 1, 2018 at 5:21 AM, Duy Nguyen wrote:
>> > On Thu, Feb 1, 2018 at 4:54 PM, Eric Sunshine
>> > wrote:
>> >> I don't see that as convincing argument for two classes of
On Mon, Feb 5, 2018 at 5:46 PM, Ævar Arnfjörð Bjarmason
wrote:
>
> On Wed, Jan 31 2018, Eric Sunshine jotted:
>
>> On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy
>> wrote:
>>> This option is designed to be used by git-completion.bash. For many
>>> simple cases, what we do in there is usua
On Wed, Jan 31 2018, Eric Sunshine jotted:
> On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy
> wrote:
>> This option is designed to be used by git-completion.bash. For many
>> simple cases, what we do in there is usually
>>
>> __gitcomp "lots of completion options"
>>
>> which has to
On Thu, Feb 01, 2018 at 02:16:46PM -0500, Eric Sunshine wrote:
> On Thu, Feb 1, 2018 at 5:21 AM, Duy Nguyen wrote:
> > On Thu, Feb 1, 2018 at 4:54 PM, Eric Sunshine
> > wrote:
> >> I don't see that as convincing argument for two classes of "no
> >> complete". Since git-completion.bash already sp
On Thu, Feb 1, 2018 at 5:21 AM, Duy Nguyen wrote:
> On Thu, Feb 1, 2018 at 4:54 PM, Eric Sunshine wrote:
>> I don't see that as convincing argument for two classes of "no
>> complete". Since git-completion.bash already special-cases
>> rebase/am/cherry-pick for --continue|--abort|--skip, it is no
On Thu, Feb 1, 2018 at 4:54 PM, Eric Sunshine wrote:
> On Wed, Jan 31, 2018 at 7:05 PM, Duy Nguyen wrote:
>> On Thu, Feb 1, 2018 at 4:04 AM, Eric Sunshine
>> wrote:
>>> On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy
>>> wrote:
Dangerous/Unpopular
options could be hidden with
On Wed, Jan 31, 2018 at 7:05 PM, Duy Nguyen wrote:
> On Thu, Feb 1, 2018 at 4:04 AM, Eric Sunshine wrote:
>> On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy
>> wrote:
>>> Dangerous/Unpopular
>>> options could be hidden with the new "NOCOMPLETE" flag.
>>
>> I wonder if this option should b
On Thu, Feb 1, 2018 at 4:04 AM, Eric Sunshine wrote:
> On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy
> wrote:
>> This option is designed to be used by git-completion.bash. For many
>> simple cases, what we do in there is usually
>>
>> __gitcomp "lots of completion options"
>>
>> whic
On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy wrote:
> This option is designed to be used by git-completion.bash. For many
> simple cases, what we do in there is usually
>
> __gitcomp "lots of completion options"
>
> which has to be manually updated when a new user-visible option is
>
On Wed, Jan 31, 2018 at 6:05 AM, Nguyễn Thái Ngọc Duy wrote:
> This option is designed to be used by git-completion.bash. For many
> simple cases, what we do in there is usually
>
> __gitcomp "lots of completion options"
>
> which has to be manually updated when a new user-visible option is
>
This option is designed to be used by git-completion.bash. For many
simple cases, what we do in there is usually
__gitcomp "lots of completion options"
which has to be manually updated when a new user-visible option is
added. With support from parse-options, we can write
__gitcomp "$(git
12 matches
Mail list logo
