Andrej Shadura writes ("Bug#928704: dgit: add bash completion for command-line
options"):
> Is there anything I can do to help you with this? I also considered
> submitting the script to the bash-completion project, but it seems
> they’d have preferred if dgit shipped it ra
Hi Ian,
On Fri, 27 Dec 2019 19:04:56 +0100 Andrej Shadura
wrote:
> Hi,
>
> I’m attaching a bash completion script which performs completion for many, but
> not all options and commands.
>
> Specifically, it autocompletes the most common subcommands, but only provides
> arguments autocompletion
Hi,
I’m attaching a bash completion script which performs completion for many, but
not all options and commands.
Specifically, it autocompletes the most common subcommands, but only provides
arguments autocompletion for only two of them, import-dsc and rpush, for
practical reasons.
For dgit opti
Colin Watson writes ("Re: Bug#928704: dgit: add bash completion for
command-line options"):
> I believe that in general terms the two strategies are to enumerate all
> the possible options separately or to have some way to ask the program
> which options it supports. The bash-
On Thu, May 09, 2019 at 10:43:06AM +0100, Ian Jackson wrote:
> Colin Watson writes ("Bug#928704: dgit: add bash completion for command-line
> options"):
> > dgit has a number of rather long option names (for example though not
> > limited to the --deliberately-* family
Control: tags -1 help
Colin Watson writes ("Bug#928704: dgit: add bash completion for command-line
options"):
> dgit has a number of rather long option names (for example though not
> limited to the --deliberately-* family). Having to type these out by
> hand makes me wish
Source: dgit
Version: 8.4
Severity: wishlist
dgit has a number of rather long option names (for example though not
limited to the --deliberately-* family). Having to type these out by
hand makes me wish for bash completion support, similar to the generally
excellent completion provided by git its
7 matches
Mail list logo
