From: Ryan Zoeller <rtzoeller@rtzoeller.com>
To: git@vger.kernel.org
Cc: Ryan Zoeller <rtzoeller@rtzoeller.com>
Subject: [RFC PATCH 0/2] Support enabling bash completion of all options
Date: Wed, 19 Aug 2020 17:50:58 +0000 [thread overview]
Message-ID: <20200819175047.692962-1-rtzoeller@rtzoeller.com> (raw)
This series adds --git-completion-helper-all, which behaves similarly to
--git-completion-helper but includes options which are typically hidden.
An environment variable GIT_COMPLETION_SHOW_ALL is used to opt-in to
this behavior.
I often prototype automated tooling around git by running commands locally
until I'm satisfied with the behavior, then migrating them into a script.
Having bash completion for some of the more obscure options is useful.
I wasn't sure how to add automated tests around this without making the
tests overly brittle (e.g. depending on a verbatim list of options), so
I welcome ideas and feedback.
-Ryan
Ryan Zoeller (2):
parse-options: add --git-completion-helper-all
completion: add GIT_COMPLETION_SHOW_ALL env var
contrib/completion/git-completion.bash | 14 +++++++++++++-
parse-options.c | 18 ++++++++++++------
2 files changed, 25 insertions(+), 7 deletions(-)
--
2.28.0.260.g5fadab5a9c
next reply other threads:[~2020-08-19 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 17:50 Ryan Zoeller [this message]
2020-08-19 17:51 ` [RFC PATCH 1/2] parse-options: add --git-completion-helper-all Ryan Zoeller
2020-08-19 19:39 ` Junio C Hamano
2020-08-19 20:51 ` Ryan Zoeller
2020-08-19 21:05 ` Junio C Hamano
2020-08-19 17:51 ` [RFC PATCH 2/2] completion: add GIT_COMPLETION_SHOW_ALL env var Ryan Zoeller
2020-08-19 23:06 ` [PATCH v2 0/2] Support enabling bash completion of all options Ryan Zoeller
2020-08-19 23:06 ` [PATCH v2 1/2] parse-options: add --git-completion-helper-all Ryan Zoeller
2020-08-19 23:06 ` [PATCH v2 2/2] completion: add GIT_COMPLETION_SHOW_ALL env var Ryan Zoeller
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=20200819175047.692962-1-rtzoeller@rtzoeller.com \
--to=rtzoeller@rtzoeller.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.
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).