From: Sean Allred <allred.sean@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Custom subcommand help handlers
Date: Sat, 12 Feb 2022 16:23:52 -0600 [thread overview]
Message-ID: <87tud3wwlx.fsf@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2112202324110.347@tvgsbejvaqbjf.bet>
> I think you might need to be a bit more careful than just looking whether
> the command in question is a built-in or not. It could be delivered as a
> script or executable inside `libexec/git-core`.
I apologize, yes -- I used 'built-in' as a synonym for 'distributed with
Git', but this of course is not how this project uses the term :-)
> Of course, this might break existing users' setups where they ship a Git
> command together with a manual page.
>
> A potential remedy against that would be, as you say, a config option.
> Maybe defaulting to the manual page if `help.format` is `man`, otherwise
> defaulting to passing `--help` to the command.
It's worth noting that Git for Windows does not distribute a
manpage-viewer :-(
--
Sean Allred
prev parent reply other threads:[~2022-02-12 22:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 16:08 Custom subcommand help handlers Sean Allred
2021-12-20 11:11 ` Ævar Arnfjörð Bjarmason
2021-12-20 12:37 ` Erik Cervin Edin
2021-12-20 22:54 ` brian m. carlson
2021-12-20 23:06 ` Junio C Hamano
2021-12-21 9:12 ` Erik Cervin Edin
2021-12-22 16:19 ` Johannes Schindelin
2021-12-22 19:53 ` Junio C Hamano
2021-12-22 23:40 ` Erik Cervin Edin
2021-12-23 0:11 ` Junio C Hamano
2021-12-23 11:33 ` Erik Cervin Edin
2021-12-23 15:07 ` Philip Oakley
2021-12-24 0:16 ` Junio C Hamano
2021-12-24 11:26 ` Philip Oakley
2022-02-12 22:29 ` Sean Allred
2021-12-20 22:39 ` Johannes Schindelin
2021-12-21 2:51 ` Ævar Arnfjörð Bjarmason
2021-12-22 16:16 ` Johannes Schindelin
2021-12-22 17:44 ` Ævar Arnfjörð Bjarmason
2022-02-12 22:23 ` Sean Allred [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=87tud3wwlx.fsf@gmail.com \
--to=allred.sean@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.