From: Thiago Perrotta <tbperrotta@gmail.com>
To: git@vger.kernel.org
Cc: Thiago Perrotta <tbperrotta@gmail.com>
Subject: [PATCH 2/3] Move bash git-send-email completions to original script.
Date: Mon, 2 Aug 2021 16:49:52 -0400 [thread overview]
Message-ID: <20210802204953.229867-3-tbperrotta@gmail.com> (raw)
In-Reply-To: <20210802204953.229867-1-tbperrotta@gmail.com>
As far as bash-completion is concerned, this refactoring is a no-op.
However, this improves `git send-email --git-completion-helper`, which
was previously printing only `git format-patch` flags, to print
send-email specific flags as well.
Add a completion test for --validate which is a send-email specific
option.
Signed-off-by: Thiago Perrotta <tbperrotta@gmail.com>
---
contrib/completion/git-completion.bash | 11 +--------
git-send-email.perl | 34 ++++++++++++++++++++++++++
t/t9902-completion.sh | 3 +++
3 files changed, 38 insertions(+), 10 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 4bdd27d..1b73a4d 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -2359,16 +2359,7 @@ _git_send_email ()
return
;;
--*)
- __gitcomp_builtin send-email "--annotate --bcc --cc --cc-cmd --chain-reply-to
- --compose --confirm= --dry-run --envelope-sender
- --from --identity
- --in-reply-to --no-chain-reply-to --no-signed-off-by-cc
- --no-suppress-from --no-thread --quiet --reply-to
- --signed-off-by-cc --smtp-pass --smtp-server
- --smtp-server-port --smtp-encryption= --smtp-user
- --subject --suppress-cc= --suppress-from --thread --to
- --validate --no-validate
- $__git_format_patch_extra_options"
+ __gitcomp_builtin send-email "$__git_format_patch_extra_options"
return
;;
esac
diff --git a/git-send-email.perl b/git-send-email.perl
index e991bf3..eec78d7 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -114,6 +114,40 @@ sub usage {
}
sub completion_helper {
+ my @send_email_flags = qw/
+ --annotate
+ --bcc
+ --cc
+ --cc-cmd
+ --chain-reply-to
+ --compose
+ --confirm=
+ --dry-run
+ --envelope-sender
+ --from
+ --identity
+ --in-reply-to
+ --no-chain-reply-to
+ --no-signed-off-by-cc
+ --no-suppress-from
+ --no-thread
+ --quiet
+ --reply-to
+ --signed-off-by-cc
+ --smtp-pass
+ --smtp-server
+ --smtp-server-port
+ --smtp-encryption=
+ --smtp-user
+ --subject
+ --suppress-cc=
+ --suppress-from
+ --thread
+ --to
+ --validate
+ --no-validate
+ /;
+ print "@send_email_flags";
print Git::command('format-patch', '--git-completion-helper');
print "\n";
exit(0);
diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh
index 1157393..a4faf64 100755
--- a/t/t9902-completion.sh
+++ b/t/t9902-completion.sh
@@ -2139,6 +2139,9 @@ test_expect_success PERL 'send-email' '
--cover-from-description=Z
--cover-letter Z
EOF
+ test_completion "git send-email --val" <<-\EOF &&
+ --validate Z
+ EOF
test_completion "git send-email ma" "main "
'
--
2.32.0
next prev parent reply other threads:[~2021-08-02 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 20:49 [PATCH 0/3] git-send-email options and completion improvements Thiago Perrotta
2021-08-02 20:49 ` [PATCH 1/3] Print newline for git-send-email --git-completion-helper Thiago Perrotta
2021-08-02 20:49 ` Thiago Perrotta [this message]
2021-08-02 20:49 ` [PATCH 3/3] Expand git-send-email docs to mention format-patch options Thiago Perrotta
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=20210802204953.229867-3-tbperrotta@gmail.com \
--to=tbperrotta@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;
as well as URLs for NNTP newsgroup(s).