From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Wincent Colaiuta" <win@wincent.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Teemu Likonen" <tlikonen@iki.fi>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH] Add subcommand "help" to the list of most commonly used subcommands
Date: Thu, 5 Jun 2008 21:15:53 +0200 [thread overview]
Message-ID: <bd6139dc0806051215i3e1f1aecg26a4baa358504849@mail.gmail.com> (raw)
In-Reply-To: <F9BB4443-EDCA-4941-9852-B84535DAD097@wincent.com>
On Thu, Jun 5, 2008 at 8:42 PM, Wincent Colaiuta <win@wincent.com> wrote:
> But if the user types "git help" they'll be presented with the exact same
> list of common commands again, at which point they'll probably wonder why
> Git suggested that.
This is exactly what I meant with my earlier comment.
> Funnily enough, if they type "git help help" then they'll get the "git-help"
> man page. So, there is no command called "git-help" on the system, but from
> the user's perspective it walks, talks and quacks like all the "real"
> commands, and so they probably consider it to be one. Whether or not the
> "help" subcommand corresponds to a real executable or script is really just
> an implementation detail, I think.
I fully agree here, it doesn't matter if there is a 'git-help.sh' or
'git-help' executable, as long as from the users POV there is a 'git
help' command should we advertise it.
> Having said that, I think your suggestion is sound if it were reworded as:
>
> See 'man git' and 'git help [command]' for more information.
That would be good, since it does not advertise a git help command,
instead it advertises 'git help command', which clearly -is- a command
(since typing 'git help command' brings up a man page).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-06-05 19:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 6:48 [TOY PATCH] git wrapper: show similar command names for an unknown command Johannes Schindelin
2008-06-05 8:19 ` [PATCH] Add subcommand "help" to the list of most commonly used subcommands Teemu Likonen
2008-06-05 10:32 ` Johannes Schindelin
2008-06-05 10:52 ` Teemu Likonen
2008-06-05 10:57 ` [PATCH v2 1/2] " Teemu Likonen
2008-06-05 10:57 ` [PATCH v2 2/2] More informative short description for git-help.txt Teemu Likonen
2008-06-05 12:58 ` [PATCH] Add subcommand "help" to the list of most commonly used subcommands Johannes Schindelin
2008-06-05 11:21 ` Sverre Rabbelier
2008-06-05 13:22 ` Teemu Likonen
2008-06-05 18:13 ` Junio C Hamano
2008-06-05 18:38 ` Pieter de Bie
2008-06-05 21:15 ` Teemu Likonen
2008-06-05 21:17 ` Junio C Hamano
2008-06-06 5:11 ` David Symonds
2008-06-05 18:42 ` Wincent Colaiuta
2008-06-05 19:15 ` Sverre Rabbelier [this message]
2008-06-05 20:59 ` [TOY PATCH] git wrapper: show similar command names for an unknown command Dirk Süsserott
2008-06-05 23:00 ` Johannes Schindelin
2008-06-06 12:15 ` Robin Rosenberg
2008-06-06 14:18 ` Wincent Colaiuta
2008-06-07 7:27 ` Alex Riesen
2008-06-07 15:04 ` Johannes Schindelin
2008-06-07 17:51 ` Alex Riesen
2008-06-07 18:08 ` Junio C Hamano
2008-06-08 15:07 ` Johannes Schindelin
2008-06-08 15:14 ` Dirk Süsserott
2008-06-08 17:53 ` Junio C Hamano
2008-06-08 23:26 ` Johannes Schindelin
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=bd6139dc0806051215i3e1f1aecg26a4baa358504849@mail.gmail.com \
--to=alturin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sverre@rabbelier.nl \
--cc=tlikonen@iki.fi \
--cc=win@wincent.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).