From: Christian Couder <chriscool@tuxfamily.org>
To: しらいしななこ <nanako3@bluebottle.com>
Cc: git@vger.kernel.org, Pascal Obry <pascal@obry.net>
Subject: Re: [PATCH] Documentation: help: describe 'man.viewer' config variable.
Date: Thu, 28 Feb 2008 04:51:08 +0100 [thread overview]
Message-ID: <200802280451.08728.chriscool@tuxfamily.org> (raw)
In-Reply-To: <200802271323.m1RDNGTR025557@mi1.bluebottle.com>
Le mercredi 27 février 2008, しらいしななこ a écrit :
> Quoting Christian Couder <chriscool@tuxfamily.org>:
> > +man.viewer::
> > + Specify the program that will be used to display help in the
> > + 'man' format. See linkgit:git-help[1].
> > +
> > -i|--info::
> > - Use the 'info' program to display the manual page, instead of
> > - the 'man' program that is used by default.
> > + Display manual documentation about the command in Info
> > + format. The 'info' program will be used for that purpose.
>
> I am not a native speaker of the English language, but "manual
> documentation about" feels duplicatedly redundant, at least to me. I
> think it is more common to say "the manual page for", or "the man page
> for".
Yes, I will send an updated patch saying "manual page for" soon.
> > -m|--man::
> > - Use the 'man' program to display the manual page. This may be
> > - used to override a value set in the 'help.format'
> > - configuration variable.
> > + Display manual documentation about the command in Man format.
>
> An earlier description for man.viewer says "in the 'man' format".
Ok, it will say "'man' format" everywhere.
> > + This option may be used to override a value set in the
> > + 'help.format' configuration variable.
> > ++
> > +By default the 'man' program will be used to display the man pages,
>
> And this part says "the man pages".
>
> > -w|--web::
> > - Use a web browser to display the HTML manual page, instead of
> > - the 'man' program that is used by default.
> > + Display manual documentation about the command in HTLM format.
> > + A web browser will be used for that purpose.
>
> Is this a mistyped "HTML format"?
Right, it will be fixed.
Thanks,
Christian.
next parent reply other threads:[~2008-02-28 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802271323.m1RDNGTR025557@mi1.bluebottle.com>
2008-02-28 3:51 ` Christian Couder [this message]
2008-02-27 5:55 [PATCH] Documentation: help: describe 'man.viewer' config variable Christian Couder
2008-02-27 13:22 ` しらいしななこ
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=200802280451.08728.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=nanako3@bluebottle.com \
--cc=pascal@obry.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).