From: Philip Oakley <philipoakley@iee.email>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"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: Fri, 24 Dec 2021 11:26:04 +0000 [thread overview]
Message-ID: <7c98ad08-046c-d2c2-2bfa-e6b559f41fd3@iee.email> (raw)
In-Reply-To: <xmqqh7ay6en7.fsf@gitster.g>
On 24/12/2021 00:16, Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.email> writes:
>
>> They had the issue that their windows users, using Git for Windows, do
>> not have the `man` package installed. Rather the `web` help of using the
>> .html version of the man page is used (needs administrator install in
>> some case). So user commands would need to provide both the man page for
>> Linux systems and some process to get the html equivalent into the right
>> folder - this latter case was the problem step.
> So are they willing to prepare `web` help pages, because that is
> what the users of Git for Windows are already familiar with, if "git
> foo --help" is capable of showing it, just like "git commit --help"
> shows the `web` help page for the subcommand?
>
> As I said elsewhere on this thread, lack of equivalent for MANPATH
> and INFOPATH makes `web` help harder to customize in that direction,
> but that is a problem we can solve in our code. Once it is there,
> they can let the user install their `web` help pages into somewhere
> the user has write access to and point at the "folder" with
> GIT_HTMLPATH, I would presume?
>
> Thanks.
>
I'm not sure if they are willing to create web versions of the man page
or not. The request was that we should let their code decide by passing
the --help option so they could link out to whatever process they have -
maybe it's a SharePoint server with fancy presentations (I never liked
them, but many places have drunk the cool aid).
Having an alternate GIT_HTMLPATH could help some users who do have html
documents, but I was cautious about letting ourselves over automate the
mechanisation and still leave the users out of the picture.
Hopefully Sean will be able to clarify if I've misunderstood the details
of their problems.
Philip
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2021-12-24 11:26 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 [this message]
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=7c98ad08-046c-d2c2-2bfa-e6b559f41fd3@iee.email \
--to=philipoakley@iee.email \
--cc=Johannes.Schindelin@gmx.de \
--cc=allred.sean@gmail.com \
--cc=avarab@gmail.com \
--cc=erik@cervined.in \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).