From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Erik Cervin Edin" <erik@cervined.in>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Sean Allred" <allred.sean@gmail.com>,
git@vger.kernel.org
Subject: Re: Custom subcommand help handlers
Date: Wed, 22 Dec 2021 11:53:41 -0800 [thread overview]
Message-ID: <xmqqczloju0q.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2112221717440.347@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 22 Dec 2021 17:19:58 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Mon, 20 Dec 2021, Junio C Hamano wrote:
>
>> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>>
>> > I should point out that in most cases on Unix, it _is_ expected that you
>> > install your manual pages into the same place as everyone else, so in
>> > this case, installing the HTML documentation alongside Git's may be the
>> > best solution.
>>
>> Yup, that sounds like the most sensible way to do things.
>
> So what about `~/bin/git-my-reply-to-junio`? Do we expect people to write
> a manual page and install it into `~/man/man1` and for `man` to pick that
> up?
Yes, if they write one, and then tell man that you have extra
manpages there via MANPATH.
I expect people *not* to write a manual page in practice for such a
thing, though ;-)
next prev parent reply other threads:[~2021-12-22 19:53 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 [this message]
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
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=xmqqczloju0q.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=allred.sean@gmail.com \
--cc=avarab@gmail.com \
--cc=erik@cervined.in \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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.