All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: <git@vger.kernel.org>
Cc: "Britton Leo Kerin" <britton.kerin@gmail.com>
Subject: Re: [PATCH v2 1/1] completion: don't complete revs when --no-format-patch
Date: Wed, 07 Feb 2024 14:12:00 -0800	[thread overview]
Message-ID: <xmqq4jej6i1b.fsf@gitster.g> (raw)
In-Reply-To: <a718b5ee-afb0-44bd-a299-3208fac43506@smtp-relay.sendinblue.com> (Britton Leo Kerin's message of "Mon, 8 Jan 2024 16:08:30 -0900")

"Britton Leo Kerin" <britton.kerin@gmail.com> writes:

> In this case the user has specifically said they don't want send-email
> to run format-patch so revs aren't valid argument completions (and it's
> likely revs and dirs do have some same names or prefixes as in
> Documentation/MyFirstContribution.txt 'psuh').
>
> Signed-off-by: Britton Leo Kerin <britton.kerin@gmail.com>
> ---
>  contrib/completion/git-completion.bash | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)

Any reviews people want to offer to this one?

Thanks.

> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 185b47d802..c983f3b2ab 100644
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -1242,10 +1242,12 @@ __git_find_last_on_cmdline ()
>  	while test $# -gt 1; do
>  		case "$1" in
>  		--show-idx)	show_idx=y ;;
> +		--)		shift && break ;;
>  		*)		return 1 ;;
>  		esac
>  		shift
>  	done
> +	[ $# -eq 1 ] || return 1   # return 1 if we got wrong # of non-opts
>  	local wordlist="$1"
>  
>  	while [ $c -gt "$__git_cmd_idx" ]; do
> @@ -2429,7 +2431,9 @@ _git_send_email ()
>  		return
>  		;;
>  	esac
> -	__git_complete_revlist
> +	if [ "$(__git_find_last_on_cmdline -- "--format-patch --no-format-patch")" != "--no-format-patch" ]; then
> +		__git_complete_revlist
> +	fi
>  }
>  
>  _git_stage ()

  reply	other threads:[~2024-02-07 22:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  9:36 [PATCH 0/1] completion: send-email: don't complete revs when --no-format-patch Britton Leo Kerin
2024-01-08  9:40 ` Dragan Simic
2024-01-08 19:34   ` Britton Kerin
2024-01-09  1:08 ` [PATCH v2 0/1] completion: " Britton Leo Kerin
     [not found] ` <20240109010830.458775-1-britton.kerin@gmail.com>
2024-01-09  1:08   ` [PATCH v2 1/1] " Britton Leo Kerin
2024-02-07 22:12     ` Junio C Hamano [this message]
2024-02-08  7:57     ` Patrick Steinhardt
2024-02-14 20:49       ` Britton Kerin
2024-02-21  1:34         ` Junio C Hamano
2024-03-05 21:58         ` Junio C Hamano
2024-04-28 22:55         ` 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=xmqq4jej6i1b.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=britton.kerin@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 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.