git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: git@vger.kernel.org
Subject: groff .ft command use in asciidoc
Date: Wed, 17 Nov 2010 10:52:34 +0100	[thread overview]
Message-ID: <20101117095233.GA23817@basil.fritz.box> (raw)


Hi,

The git manpages on my opensuse 11.3 (git 1.7.1-1.14)
frequently use the .ft command the opensuse groff does not 
render.

For example from the final output of "man git-commit":

           .ft C
           $ edit hello.c
           $ git rm goodbye.c
           $ git add hello.c
           $ git commit
           .ft


So the .ft commands are visible.  It's really a cosmetic issue 
only, but looks ugly and irritates me every time I 
look something up in the man pages.

I double checked against current git.git and the problem 
is still there, because .ft C is configured in 
Documentation/asciidoc.conf

Not sure what the best solution is. Stop using .ft
and change asciidocs configuration?


-Andi 


-- 
ak@linux.intel.com -- Speaking for myself only.

             reply	other threads:[~2010-11-17  9:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  9:52 Andi Kleen [this message]
2010-11-17 10:15 ` groff .ft command use in asciidoc Jonathan Nieder
2010-11-17 11:52   ` Andi Kleen
2010-11-17 14:38   ` Jeff King
2010-11-17 15:48     ` Andi Kleen
2010-11-19 17:54       ` Jeff King
2010-11-19 18:22         ` Jonathan Nieder
2010-11-19 18:37           ` Jeff King
2010-11-19 20:34         ` Drew Northup
2010-11-19 20:40           ` Jeff King
2010-11-19 20:53             ` Drew Northup
2010-11-19 22:58             ` Junio C Hamano
2010-11-20  1:48               ` Todd Zullinger
2010-11-18 17:47   ` Alejandro Riveira Fernández
2010-11-18 21:11     ` Drew Northup
2010-11-18 23:15       ` Alejandro Riveira Fernández

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=20101117095233.GA23817@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=git@vger.kernel.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).