From: Christian Couder <chriscool@tuxfamily.org>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-help: Try to find html pages without the git- prefix
Date: Tue, 29 Apr 2008 05:13:40 +0200 [thread overview]
Message-ID: <200804290513.40948.chriscool@tuxfamily.org> (raw)
In-Reply-To: <1209377611-90005-1-git-send-email-pdebie@ai.rug.nl>
Le lundi 28 avril 2008, Pieter de Bie a écrit :
> Some html documentation does not have the git- prefix, for example
> hooks.html. If the git-command.html page does not exist, try to find the
> command.html file. This allows commands like `git help -w hooks' to work
Yes, this works fine for html documentation.
But 'git help -w githooks' could work fine too, if the source filename
was "githooks.txt" instead of "hooks.txt". Because the "cmd_to_page"
function returns its input as is, if it starts with "git".
And with more filenames like "githooks.txt" we could also have
more "githooks" like regular man pages without poluting too much the man
page namespace.
We already have the following files following that scheme:
gitk.txt
gitattributes.txt
gitignore.txt
gitcli.txt
gitmodules.txt
git.txt
And for example the following commands are already working:
$ git help -w gitmodules
$ git help -m gitmodules
$ man gitmodules
("git help -i gitmodules" should work too, but info format help seems
broken.)
Of course typing "git help hooks" is shorter and simpler than "git help
githooks", so it could perhaps still be a good idea to try "gitXXX" as a
fallback if we find nothing for "git-XXX".
Thanks,
Christian.
next prev parent reply other threads:[~2008-04-29 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 10:13 [PATCH] git-help: Try to find html pages without the git- prefix Pieter de Bie
2008-04-29 3:13 ` Christian Couder [this message]
2008-04-29 4:45 ` Junio C Hamano
2008-04-29 5:18 ` Christian Couder
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=200804290513.40948.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=pdebie@ai.rug.nl \
/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).