From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git help: promote 'git help -av'
Date: Sat, 22 Sep 2018 21:29:18 +0200 [thread overview]
Message-ID: <87fty1jppt.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20180922174707.16498-1-pclouds@gmail.com>
On Sat, Sep 22 2018, Nguyễn Thái Ngọc Duy wrote:
> When you type "git help" (or just "git") you are greeted with a list
> with commonly used commands and their short description and are
> suggested to use "git help -a" or "git help -g" for more details.
>
> "git help -av" would be more friendly and inline with what is shown
> with "git help" since it shows list of commands with description as
> well, and commands are properly grouped.
>
> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
> ---
> git.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/git.c b/git.c
> index a6f4b44af5..69c21f378b 100644
> --- a/git.c
> +++ b/git.c
> @@ -31,7 +31,7 @@ const char git_usage_string[] =
> " <command> [<args>]");
>
> const char git_more_info_string[] =
> - N_("'git help -a' and 'git help -g' list available subcommands and some\n"
> + N_("'git help -av' and 'git help -g' list available subcommands and some\n"
> "concept guides. See 'git help <command>' or 'git help <concept>'\n"
> "to read about a specific subcommand or concept.");
A side-effect of this not noted in your commit message is that we'll now
invoke the pager, perhaps we should just do:
diff --git a/builtin/help.c b/builtin/help.c
index 8d4f6dd301..1a3b174aaf 100644
--- a/builtin/help.c
+++ b/builtin/help.c
@@ -436,9 +436,9 @@ int cmd_help(int argc, const char **argv, const char *prefix)
parsed_help_format = help_format;
if (show_all) {
+ setup_pager();
git_config(git_help_config, NULL);
if (verbose) {
- setup_pager();
list_all_cmds_help();
return 0;
}
@@ -460,8 +460,10 @@ int cmd_help(int argc, const char **argv, const char *prefix)
return 0;
}
- if (show_guides)
+ if (show_guides) {
+ setup_pager();
list_common_guides_help();
+ }
if (show_all || show_guides) {
printf("%s\n", _(git_more_info_string));
Or is there a good reason we shouldn't invoke the pager for e.g. -g when
the terminal is too small (per our default less config)?
Another thing I noticed: We don't list -v in the git-help manpage, but
since we use OPT_VERBOSE it's supported.
next prev parent reply other threads:[~2018-09-22 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 17:47 [PATCH] git help: promote 'git help -av' Nguyễn Thái Ngọc Duy
2018-09-22 19:29 ` Ævar Arnfjörð Bjarmason [this message]
2018-09-23 6:51 ` Duy Nguyen
2018-09-24 18:19 ` Jeff King
2018-09-24 20:20 ` Taylor Blau
2018-09-24 20:30 ` Jeff King
2018-09-24 20:58 ` Junio C Hamano
2018-09-25 15:15 ` Duy Nguyen
2018-09-25 17:44 ` Duy Nguyen
2018-09-25 20:54 ` Jeff King
2018-09-26 16:18 ` Duy Nguyen
2018-09-26 17:25 ` Junio C Hamano
2018-09-26 17:28 ` Junio C Hamano
2018-09-28 2:37 ` Taylor Blau
2018-09-28 16:30 ` Junio C Hamano
2018-09-28 17:49 ` Taylor Blau
2018-09-29 6:08 ` [PATCH v2] help -a: improve and make --verbose default Nguyễn Thái Ngọc Duy
2018-10-01 18:14 ` Taylor Blau
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=87fty1jppt.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).