From: "Pablo Sabater" <pabloosabaterr@gmail.com>
To: "Mirko Faina" <mroik@delayed.space>, <git@vger.kernel.org>
Cc: <toon@iotcl.com>
Subject: Re: [PATCH] bash-completions: add --[no-]graph-indent
Date: Thu, 29 Oct 2026 13:45:15 +0000 [thread overview]
Message-ID: <DMHD8RCO7V74.2BK7C9T4HNLHO@gmail.com> (raw)
In-Reply-To: <63106e1dec45e82c7f132a18816b2d1fffb52752.1791921033.git.mroik@delayed.space>
[Cc'd Toon because of the mention]
On Tue Oct 13, 2026 at 8:50 PM WEST, Mirko Faina wrote:
> Add missing completion for "git log --graph-indent" and "git log
> --no-graph-indent".
>
> Signed-off-by: Mirko Faina <mroik@delayed.space>
> ---
> contrib/completion/git-completion.bash | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index c3a49e2e22..2348a3cfb9 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -2298,6 +2298,7 @@ __git_log_common_options="
> --right-only --show-linear-break
> --show-notes-by-default --show-pulls
> --since-as-filter --single-worktree
> + --graph-indent --no-graph-indent
Thanks for Cc'ing.
I didn't know about this so I completely forgot to add it, however from
what I read, this is the __git_log_common_options and I'm not sure if
this is a "common" opt, as I don't even see --graph here.
I searched where --graph is, and it's here:
l 2383-2409 'git-completion.bash'
__gitcomp "
[more opts]
--graph
[more opts]
$merge
$__git_diff_common_options
"
return
;;
I think it would fit better here (not sure, I just quickly skimmed the
file).
Also, I missed this for the --graph-lane-limit option so maybe it should
be added too?
My main doubt is, both these options proposed (yours and
--graph-lane-limit) are --graph dependent, which means if someone
autocompletes them but doesn't use --graph, they will get an error
saying that --graph is needed. I'd say we do what other --graph
dependent options do, but AFAIK these two are the only ones.
From Toon's Git Merge talk, more options for --graph option will be
developed so we should maybe think about how to do it in a way that
doesn't autocomplete if it's going to error? (maybe that does exist,
given the multiple options that depend on other options)
> "
> # Options that go well for log and gitk (not shortlog)
> __git_log_gitk_options="
>
> base-commit: 6de20f6092dcf9bdb1c8efe03db4b70c82b423dd
Thanks,
Pablo
next prev parent reply other threads:[~2026-10-29 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 19:50 [PATCH] bash-completions: add --[no-]graph-indent Mirko Faina
2026-10-29 12:16 ` Mirko Faina
2026-10-29 13:45 ` Pablo Sabater [this message]
2026-10-29 14:17 ` Ben Knoble
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DMHD8RCO7V74.2BK7C9T4HNLHO@gmail.com \
--to=pabloosabaterr@gmail.com \
--cc=git@vger.kernel.org \
--cc=mroik@delayed.space \
--cc=toon@iotcl.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.