From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] parse-options: fix completion format when first option is skipped
Date: Thu, 01 Oct 2026 10:38:08 -0700 [thread overview]
Message-ID: <xmqqik3l5njz.fsf@gitster.g> (raw)
In-Reply-To: <20261001-b4-pks-parse-options-subcommand-groups-v1-1-01eb2f4a4c32@pks.im> (Patrick Steinhardt's message of "Thu, 01 Oct 2026 12:13:28 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> The "--git-completion-helper" option can be passed to any command or
> subcommand that uses the parse-options interface. The output it
> generates is a space-separated list of subcommands or options understood
> by the command.
>
> The format is slightly broken though in the case where the first option
> is not being printed, like for example a group or a hidden option. In
> that case, `show_gitcomp()` will of course skip that first entry. But
> when printing the next option it checks for `opts == original_opts` to
> verify whether we're printing the first option. The check will evaluate
> to false though as we have skipped it, and thus we'll print a leading
> space even though we have printed nothing else yet.
>
> Fix that bug by tracking whether we have already printed anything via a
> local variable.
Very clearly articulated. I would have chosen 'shown' as the
variable name to so do, but 'first' may also be OK.
>
> Signed-off-by: Patrick Steinhardt <ps@pks.im>
> ---
> parse-options.c | 4 +++-
> t/helper/test-parse-options.c | 1 +
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/parse-options.c b/parse-options.c
> index 4519ead9dc..356eeff016 100644
> --- a/parse-options.c
> +++ b/parse-options.c
> @@ -845,6 +845,7 @@ static int show_gitcomp(const struct option *opts, int show_all)
> {
> const struct option *original_opts = opts;
> int nr_noopts = 0;
> + bool first = true;
>
> for (; opts->type != OPTION_END; opts++) {
> const char *prefix = "--";
> @@ -882,8 +883,9 @@ static int show_gitcomp(const struct option *opts, int show_all)
> suffix = "=";
> if (starts_with(opts->long_name, "no-"))
> nr_noopts++;
> - printf("%s%s%s%s", opts == original_opts ? "" : " ",
> + printf("%s%s%s%s", first ? "" : " ",
> prefix, opts->long_name, suffix);
> + first = false;
> }
> show_negated_gitcomp(original_opts, show_all, -1);
> show_negated_gitcomp(original_opts, show_all, nr_noopts);
> diff --git a/t/helper/test-parse-options.c b/t/helper/test-parse-options.c
> index f181f0c02d..fbafd67756 100644
> --- a/t/helper/test-parse-options.c
> +++ b/t/helper/test-parse-options.c
> @@ -351,6 +351,7 @@ static int parse_subcommand__cmd(int argc, const char **argv,
> parse_opt_subcommand_fn *fn = NULL;
> int opt = 0;
> struct option options[] = {
> + OPT_GROUP("Subcommands"),
> OPT_SUBCOMMAND("subcmd-one", &fn, subcmd_one),
> OPT_SUBCOMMAND("subcmd-two", &fn, subcmd_two),
> OPT_INTEGER('o', "opt", &opt, "an integer option"),
next prev parent reply other threads:[~2026-10-01 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 10:13 [PATCH 0/3] builtin/refs: introduce subcommand groups Patrick Steinhardt
2026-10-01 10:13 ` [PATCH 1/3] parse-options: fix completion format when first option is skipped Patrick Steinhardt
2026-10-01 17:38 ` Junio C Hamano [this message]
2026-10-02 7:19 ` Patrick Steinhardt
2026-10-01 10:13 ` [PATCH 2/3] parse-options: allow grouping subcommands Patrick Steinhardt
2026-10-01 17:46 ` Junio C Hamano
2026-10-02 7:19 ` Patrick Steinhardt
2026-10-01 10:13 ` [PATCH 3/3] builtin/refs: introduce subcommand groups Patrick Steinhardt
2026-10-01 17:46 ` Junio C Hamano
2026-10-02 8:09 ` [PATCH v2 0/4] " Patrick Steinhardt
2026-10-02 8:09 ` [PATCH v2 1/4] parse-options: fix completion format when first option is skipped Patrick Steinhardt
2026-10-02 8:09 ` [PATCH v2 2/4] parse-options: extract functions to print single option Patrick Steinhardt
2026-10-02 8:09 ` [PATCH v2 3/4] parse-options: allow grouping subcommands Patrick Steinhardt
2026-10-02 8:09 ` [PATCH v2 4/4] builtin/refs: introduce subcommand groups Patrick Steinhardt
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=xmqqik3l5njz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox