From: Jeff King <peff@peff.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git help: promote 'git help -av'
Date: Mon, 24 Sep 2018 16:30:49 -0400 [thread overview]
Message-ID: <20180924203049.GA26044@sigill.intra.peff.net> (raw)
In-Reply-To: <20180924202000.GA88744@syl>
On Mon, Sep 24, 2018 at 03:20:00PM -0500, Taylor Blau wrote:
> On Mon, Sep 24, 2018 at 02:19:28PM -0400, Jeff King wrote:
> > On Sat, Sep 22, 2018 at 07:47:07PM +0200, 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.
> >
> > I agree that "help -av" is likely to be more friendly. I kind of wonder
> > if it should just be the default for "-a". Do we have any obligation not
> > to change the format of that output?
>
> I agree, though I'd like to clarify what you said before doing so
> wholeheartedly.
>
> Did you mean that all existing uses of 'git help -a' should instead mean
> 'git help -av' (i.e., that '-a' after your proposed patch means the same
> as '-av' in revisions prior to this one?)
Yes, exactly. I think the vast majority of uses would prefer the
categorized list.
The obvious exceptions are:
- you can't remember the name of the command so an alphabetized list is
easier for sifting through (without having to re-sift for each
category).
- you need a machine-readable version of the list (e.g., for
programmable completion). We have "git --list-cmds", but we may need
to advertise it better and mark it non-experimental.
I dunno. Maybe it is not worth the effort. Duy's existing patch is an
easy one liner. ;)
-Peff
next prev parent reply other threads:[~2018-09-24 20:30 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
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 [this message]
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=20180924203049.GA26044@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--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).