git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Robert Karszniewicz <avoidr@posteo.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-completion.bash: stash-show: add --patch-with-stat
Date: Wed, 30 Sep 2020 12:09:09 -0700	[thread overview]
Message-ID: <xmqqo8lngjze.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200929213154.GA18321@HP> (Robert Karszniewicz's message of "Tue, 29 Sep 2020 23:31:54 +0200")

Robert Karszniewicz <avoidr@posteo.de> writes:

>> surprising experience to the end users.  For "show" alone, it may
>> make a lot of sense to complete "git stash show -<TAB>" and offer
>> "-p".
>
> Does git complete short options at all? I only see long options
> completed. (I'm also very new to bash-completion)

I wouldn't personally recommend it, but I did see a patch that added
support for one short option completion quite recently.  As long as
"--<TAB>" gets completed to often-used options, among which "--patch"
and "--stat" are included, it would be OK not to react to "-<TAB>".

>> In any case, it might make more sense to do this instead, and then
>> rethink what options make sense to these subcommands of "git stash".
>> I do not think patch-with-stat should be among them.
>
> So shall I do a v2 as per your suggestion and replace
> "--patch-with-stat" with "--patch --stat"?

I think Denton Liu offered a different suggestion; I didn't look at
and compare which direction is the better one myself, but an
approach that keeps the number of manually-maintained list of
options low is almost always a good approach.

Thanks.

  reply	other threads:[~2020-09-30 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 11:05 [PATCH] git-completion.bash: stash-show: add --patch-with-stat Robert Karszniewicz
2020-09-28 18:43 ` Junio C Hamano
2020-09-29  6:25   ` Denton Liu
2020-09-29 21:31   ` Robert Karszniewicz
2020-09-30 19:09     ` Junio C Hamano [this message]
2020-09-30 21:56       ` Robert Karszniewicz

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqo8lngjze.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avoidr@posteo.de \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).