From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: git@vger.kernel.org
Subject: Re: groff .ft command use in asciidoc
Date: Fri, 19 Nov 2010 00:15:14 +0100 [thread overview]
Message-ID: <20101119001514.4cd0c4d9@varda> (raw)
In-Reply-To: <1290114671.2316.12.camel@drew-northup.unet.maine.edu>
El Thu, 18 Nov 2010 16:11:11 -0500
Drew Northup <drew.northup@maine.edu> escribió:
>
> On Thu, 2010-11-18 at 17:47 +0000, Alejandro Riveira Fernández wrote:
> > On Wed, 17 Nov 2010 04:15:16 -0600, Jonathan Nieder wrote:
>
> > > This is in my opinion a bug: unless you use ASCIIDOC_NO_ROFF, git's
> > > asciidoc.conf will include raw roff directives in the docbook markup it
> > > generates. And then docbook will escape the periods, producing the
> > > output you see.
> > >
> > > The workaround is very simple: set ASCIIDOC_NO_ROFF to nonempty when you
> > > build documentation.
> >
> > I use make quick-install-man which, afaik, installs man pages
> > "prerendered" from the man branch and i see the same artifact.
> >
> > So can those man pages be rendered with this workaraound?
> >
> > Thanks
>
> Out of curiosity I went ahead and ran that make script. I then ran the
> following in the directory that the manpage directories were written out
> to (an alternate DESTDIR):
Doh! ... the problem was between chair and keyboard. i used alternate DESTDIR
with the make all and make install but with quick.-install-man i forgot to set
it; so the man pages were old versions from when i actually builded the man
pages myself
Sorry for the wasted time ...
>
> [dnorthup@drew-northup man]$ grep -R "\.ft" *
> [dnorthup@drew-northup man]$
>
After correcting the above
$ grep -R "\.ft" *
man3/private-Error.3pm:.ft CW
man3/private-Error.3pm:.ft R
man3/Git.3pm:.ft CW
man3/Git.3pm:.ft R
Which are probably letfovers from previous builds ...
> Note that it returned nothing. This is based on the current git.git. (I
> just pulled to be sure of that...)
Thanks for checking and again. Sorry
>
> As noted, all that make script essentially does is write out the
> manpages found in origin/man--so it matters not what my current platform
> is.
>
> Run "man git-commit" in one terminal open up a second and run "ps ax |
> grep man" and report on the results.
For the sake of completeness
$ ps ax | grep man
585 ? S< 0:00 [kondemand]
4994 ? S 0:00 gnome-power-manager
32649 pts/2 S+ 0:00 man git-commit
32690 pts/4 S+ 0:00 grep man
Bye.
prev parent reply other threads:[~2010-11-18 23:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 9:52 groff .ft command use in asciidoc Andi Kleen
2010-11-17 10:15 ` 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 [this message]
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=20101119001514.4cd0c4d9@varda \
--to=ariveira@gmail.com \
--cc=drew.northup@maine.edu \
--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).