From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Modified the default git help message to be grouped by topic
Date: Wed, 03 Dec 2008 01:47:56 +0100 [thread overview]
Message-ID: <gh4kub$rh3$1@ger.gmane.org> (raw)
In-Reply-To: 7vfxl6m84g.fsf@gitster.siamese.dyndns.org
Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
>> On Tue, Dec 02, 2008 at 11:55:03PM +0100, Johannes Schindelin wrote:
>>
>>> If the whole thing gets longer than 24 lines, we have to leave some things
>>> out. Personally, I consider rm and mv unimportant enough that they could
>>> be shown in an extended list, but be left out of the summary page.
>>
>> For the record, the current output is 26 lines, plus you probably want
>> to account for 1 line of the user's next shell prompt. So we are 3 lines
>> over already.
>>
>> Scott's proposal is about grouping the commands more sensibly. Many of
>> the complaints are about the length of the output. Maybe we should scrap
>> having a list of commands altogether and just point at section-specific
>> documentation, each of which could discuss basic commands related to it.
>>
>> I think there has been mention of task-oriented documentation pointers
>> before, and I think this is a place where we would want it.
>
> It might not be a bad idea to make this "top page help" into an
> interactive hierarchical help topic browser.
Isn't that info?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-12-03 0:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 17:30 [PATCH] Modified the default git help message to be grouped by topic Scott Chacon
2008-12-01 18:32 ` Jeff King
2008-12-02 1:45 ` Junio C Hamano
2008-12-02 6:10 ` Scott Chacon
2008-12-02 20:11 ` James Pickens
2008-12-02 21:33 ` Boyd Stephen Smith Jr.
2008-12-02 22:55 ` Johannes Schindelin
2008-12-02 23:30 ` Jeff King
2008-12-02 23:39 ` Scott Chacon
2008-12-03 0:10 ` Junio C Hamano
2008-12-03 0:37 ` Jeff King
2008-12-03 0:47 ` Jakub Narebski [this message]
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='gh4kub$rh3$1@ger.gmane.org' \
--to=jnareb@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.