From: Patrick Steinhardt <ps@pks.im>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 0/5] stash completion miscellany
Date: Mon, 26 Oct 2026 09:48:11 +0100 [thread overview]
Message-ID: <at8TywNz2WcDc-0c@pks.im> (raw)
In-Reply-To: <cover.1792761643.git.ben.knoble@gmail.com>
On Fri, Oct 23, 2026 at 09:20:50AM -0400, D. Ben Knoble wrote:
> Diff-intervalle contre v1 :
> 1: d0e461a14a ! 1: 90d36b6445 completion: simplify stash subcommand completion
> @@ Commit message
> The stash completion helper contains a hard-coded list of commands, but
> git-stash provides a mechanism to list such commands
> (--git-completion-helper). The pattern for using it is wrapped by
> - __git_resolve_builtins, so use it, bring _git_stash closer in line with
> - other completion helpers.
> + __git_resolve_builtins, so use it, bringing _git_stash closer in line
> + with other completion helpers. As a nice side-benefit, this also adds
> + "store" subcommand completion, which is missing from the explicit list
> + of subcommands.
Yup.
> - Note that we maintain the "save" special case, since it was removed from
> + Note that we maintain the "save" special case†, since it was removed from
> default completion in 0eb5a4f911 (completion: stop showing 'save' for
> - stash by default, 2018-04-20). We don't have to do anything special with
> - the exclude (3rd) argument to __git_resolve_builtins, though, because
> - save is already marked PARSE_OPT_NOCOMPLETE.
> + stash by default, 2018-04-20). One might think we need to give "save" to
> + __git_resolve_builtins' 3rd exclude argument to prevent it from
> + showing up, but we don't: "save" is already marked PARSE_OPT_NOCOMPLETE.
> +
> + †We don't complete the "save" subcommand unless at least "sa" has been
> + typed, but we do complete its options if explicitly typed. With this
> + change, we will complete "save" if GIT_COMPLETION_SHOW_ALL=1.
Good.
> 5: d1d0bf2d9a ! 5: 0266646fb4 completion: drop "stash save" completion altogether
> @@ Commit message
> further documentation suggesting to use it.
>
> Since we recommend push instead, stop completing for "save" and remove a
> - special case in completion code.
> + special case in completion code. It still appears for "git stash <tab>"
> + when GIT_COMPLETION_SHOW_ALL=1, and when typed explicitly we still
> + complete options for
> +
> + git stash save --<tab>
> +
> + which is helpful for folks with finger-memory for save.
Agreed, documenting the status quo feels reasonable to me.
So overall I'm happy with this v2, thanks!
Patrick
next prev parent reply other threads:[~2026-10-26 8:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 17:48 [PATCH 0/5] stash completion miscellany D. Ben Knoble
2026-10-12 17:48 ` [PATCH 1/5] completion: simplify stash subcommand completion D. Ben Knoble
2026-10-16 8:01 ` Patrick Steinhardt
2026-10-19 19:58 ` Ben Knoble
2026-10-12 17:48 ` [PATCH 2/5] completion: extract common stash listing code D. Ben Knoble
2026-10-12 17:48 ` [PATCH 3/5] completion: fix Zsh handling of stash names D. Ben Knoble
2026-10-16 8:01 ` Patrick Steinhardt
2026-10-19 19:56 ` Ben Knoble
2026-10-12 17:48 ` [PATCH 4/5] doc: drop usage mentions of "git stash save" D. Ben Knoble
2026-10-16 8:01 ` Patrick Steinhardt
2026-10-12 17:48 ` [PATCH 5/5] completion: drop "stash save" completion altogether D. Ben Knoble
2026-10-16 8:01 ` Patrick Steinhardt
2026-10-19 20:01 ` Ben Knoble
2026-10-20 6:05 ` Patrick Steinhardt
2026-10-22 13:14 ` D. Ben Knoble
2026-10-23 6:21 ` Patrick Steinhardt
2026-10-23 13:20 ` [PATCH v2 0/5] stash completion miscellany D. Ben Knoble
2026-10-23 13:20 ` [PATCH v2 1/5] completion: simplify stash subcommand completion D. Ben Knoble
2026-10-23 13:20 ` [PATCH v2 2/5] Completion: extract common stash listing code D. Ben Knoble
2026-10-23 17:06 ` Junio C Hamano
2026-10-23 13:20 ` [PATCH v2 3/5] completion: fix Zsh handling of stash names D. Ben Knoble
2026-10-23 13:20 ` [PATCH v2 4/5] doc: drop usage mentions of "git stash save" D. Ben Knoble
2026-10-23 13:20 ` [PATCH v2 5/5] completion: drop "stash save" completion altogether D. Ben Knoble
2026-10-23 17:06 ` Junio C Hamano
2026-10-23 18:07 ` Ben Knoble
2026-10-23 14:33 ` [PATCH v2 0/5] stash completion miscellany Kristoffer Haugsbakk
2026-10-26 8:48 ` Patrick Steinhardt [this message]
2026-10-26 14:30 ` Junio C Hamano
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=at8TywNz2WcDc-0c@pks.im \
--to=ps@pks.im \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
/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