From: Jeff King <peff@peff.net>
To: Vincent van Ravesteijn <vfr@lyx.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Add the possibility to specify a default help format
Date: Wed, 6 Jun 2012 09:53:53 -0400 [thread overview]
Message-ID: <20120606135353.GD2597@sigill.intra.peff.net> (raw)
In-Reply-To: <1338987397-7376-1-git-send-email-vfr@lyx.org>
On Wed, Jun 06, 2012 at 12:56:37PM +0000, Vincent van Ravesteijn wrote:
> At the moment, the default help format (i.e. the format that is chosen if
> 'git help xxx' is called without a help format parameter) is defined by
> the switch to be 'man'. However, on different platforms the preferred
> format might differ. For example, on Windows there is no man viewer, so we
> would prefer html.
>
> This patch adds the possibility to choose a default help format on
> compilation by defining DEFAULT_HELP_FORMAT. If it is not specified the
> default is still 'man'.
Makes sense to me.
> ---
> builtin/help.c | 8 +++++++-
> 1 files changed, 7 insertions(+), 1 deletions(-)
Should there be some minor infrastructure in the Makefile so you can do:
make DEFAULT_HELP_FORMAT=man
rather than:
make CFLAGS='-DDEFAULT_HELP_FORMAT=\"man\"'
(and the Makefile would be a good place to advertise this build knob,
too)?
-Peff
next prev parent reply other threads:[~2012-06-06 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 12:56 [PATCH] Add the possibility to specify a default help format Vincent van Ravesteijn
2012-06-06 13:53 ` Jeff King [this message]
2012-06-06 18:51 ` [PATCH] Add the DEFAULT_HELP_FORMAT option to Makefile vfr
2012-06-06 19:06 ` Junio C Hamano
2012-06-06 20:25 ` Vincent van Ravesteijn
2012-06-06 21:07 ` Junio C Hamano
2012-06-06 20:28 ` [PATCHv2] Add the possibility to specify a default help format Vincent van Ravesteijn
2012-06-06 21:21 ` Junio C Hamano
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=20120606135353.GD2597@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vfr@lyx.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 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).