From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Stefan Tatschner <stefan@sevenbyte.org>,
git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix inconsistent quotes
Date: Wed, 29 Apr 2015 13:13:53 -0700 [thread overview]
Message-ID: <xmqqpp6m4rr2.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150429200453.GA750@peff.net> (Jeff King's message of "Wed, 29 Apr 2015 16:04:54 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Apr 29, 2015 at 12:09:46PM -0700, Jonathan Nieder wrote:
>
>> Hi,
>>
>> Jeff King wrote:
>>
>> > But IMHO, using backticks looks much better. In the roff-formatted
>> > manpages single quotes underline, but backticks use bold.
>>
>> Are you sure? My copy of git.1.gz has backticks converted into no
>> formatting at all:
>>
>> Other options are available to control how the manual page is displayed\&. See
>> \fBgit-help\fR(1)
>> for more information, because
>> git \-\-help \&.\&.\&.
>> is converted internally into
>> git help \&.\&.\&.\&.
>
> It's actually optional. See 5121a6d (Documentation: option to render
> literal text as bold for manpages, 2009-03-27). I don't see a good
> reason that wasn't made the default early, except conservatism. I've had
> it enabled for years (though I admit I don't read the manpages that much
> these days :) ).
Interesting. What I happen to use when populating the git-manpages
repository would have wider impact to the users, as I hear that some
(or many) distros just package whatever I have there. I do not mind
enabling it on my end if that gives us more readable rendition.
next prev parent reply other threads:[~2015-04-29 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 18:08 [PATCH] Documentation: Fix inconsistent quotes Stefan Tatschner
2015-04-29 18:51 ` Jeff King
2015-04-29 19:09 ` Jonathan Nieder
2015-04-29 20:04 ` Jeff King
2015-04-29 20:13 ` Junio C Hamano [this message]
2015-04-29 20:32 ` Jeff King
2015-05-14 9:14 ` Stefan Tatschner
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=xmqqpp6m4rr2.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=stefan@sevenbyte.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 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.