From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: Duy Nguyen <pclouds@gmail.com>, Git List <git@vger.kernel.org>,
Ralf Thielow <ralf.thielow@gmail.com>
Subject: Re: git glossary --help ?
Date: Mon, 08 Apr 2019 10:06:21 +0900 [thread overview]
Message-ID: <xmqqd0lxcnle.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <3de9d8bc-f9d1-bf09-def6-71e5ed418225@iee.org> (Philip Oakley's message of "Sun, 7 Apr 2019 23:42:39 +0100")
Philip Oakley <philipoakley@iee.org> writes:
>> But unlike "git foo --help", if the word that ought to name a
>> subcommand instead names a known concept, e.g. "glossary", I do not
>> think it is too bad if we DWIMmed what the user meant to say,
>> i.e. turning "git glossary --help" into "git help glossary".
>>
> Given the earlier report that started the thread Duy linked, I guess
> there will need to be a balance between the two expectations.
>
> The DWIMming may need to both report that it's not a command, but
> then offer the concept guide as the primary target if correct, or
> perhaps as one of the alternate "commands" if closely named to a guide
> (e.g. revisions vs revision).
The "or perhaps" part feels a bit overkill, but I do not mind seeing
it if somebody does it cleanly and correctly ;-)
> One of the issues back then was the lack of a complete list of
> 'guides' to check against, so the badly spelt command logic wasn't
> brought into play.
Yeah, thanks for spelling it out; I think we are on the same page,
having followed the same discussion in the archive, where we knew
that a list of 'concepts-not-commands' would help the error message
situation.
prev parent reply other threads:[~2019-04-08 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 17:31 git glossary --help ? Philip Oakley
2019-04-06 18:09 ` Andreas Schwab
2019-04-06 20:27 ` Philip Oakley
2019-04-07 3:20 ` Duy Nguyen
2019-04-07 11:52 ` Philip Oakley
2019-04-07 13:43 ` Junio C Hamano
2019-04-07 22:42 ` Philip Oakley
2019-04-08 1:06 ` Junio C Hamano [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
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=xmqqd0lxcnle.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=philipoakley@iee.org \
--cc=ralf.thielow@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.
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).