SZEDER Gábor writes:
> diff --git a/builtin/config.c b/builtin/config.c
> index 7188405..38bcf83 100644
> --- a/builtin/config.c
> +++ b/builtin/config.c
> @@ -13,6 +13,7 @@ static char *key;
> static regex_t *key_regexp;
> static regex_t *regexp;
> static int show_keys;
> +static int show_onl
Quoting Jeff King :
On Wed, May 27, 2015 at 10:07:19PM +0200, SZEDER Gábor wrote:
Help the completion script by introducing the '--list-names' and
'--get-names-regexp' options, the "names-only" equivalents of '--list' and
'--get-regexp', so it doesn't have to separate variable names from thei
On Wed, May 27, 2015 at 05:04:38PM -0400, Jeff King wrote:
> > -'git config' [] [-z|--null] -l | --list
> > +'git config' [] [-z|--null] -l | --list | --list-name
>
> s/list-name/&s/, to match the code (and your commit message).
Doh, just saw your "1.5".
FWIW, I expected "PATCH 1.5/2" to be "eh
On Wed, May 27, 2015 at 10:07:19PM +0200, SZEDER Gábor wrote:
> Help the completion script by introducing the '--list-names' and
> '--get-names-regexp' options, the "names-only" equivalents of '--list' and
> '--get-regexp', so it doesn't have to separate variable names from their
> values anymore.
Recenty I created a multi-line branch description with '.' and '='
characters on one of the lines, and noticed that fragments of that line
show up when completing set variable names for 'git config', e.g.:
$ git config --get branch.b.description
Branch description to fool the completion script
5 matches
Mail list logo
