discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: .Fn _* issue
Date: Sat, 25 Sep 2010 16:35:01 +0100	[thread overview]
Message-ID: <20100925153525.GD25298@bramka.kerhand.co.uk> (raw)
In-Reply-To: <4C9E13FE.2010001@bsd.lv>

On Sat, Sep 25, 2010 at 05:23:42PM +0200, Kristaps Dzonsons wrote:
> > so the issue is the initial `_' in _flush_cache. it's formatted in a
> > different font to the rest of the function name (you can see this best
> > on a terminal).
> > 
> > this is a long standing bug that we always had in old groff, which
> > really annoyed me. new groff fixed it.
> 
> Jason, I'm not sure I follow as mandoc, new groff, and old groff all
> seem to do the same thing with the _flush_cache beginning:
> 
>   GNU nroff (groff) version 1.18.1
>   nroff -mandoc foo.1 | hexdump -c
>   _  \b   _   f  \b   f   l  \b   l   u  \b
> 
>   mandoc foo.1 | hexdump -c
>   _  \b   _   f  \b   f   l  \b   l   u  \b
> 
>   GNU troff version 1.15
>   nroff -mandoc foo.1 | hexdump -c
>   _  \b   _   f  \b   f   l  \b   l   u  \b
> 
> 

hmm, and you do not see the issue i describe? what else could it be?
surely not my TERM setting if mandoc shows it one way and groff another.

what else?

jmc
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-09-25 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  6:35 Jason McIntyre
2010-09-25 15:23 ` Kristaps Dzonsons
2010-09-25 15:35   ` Jason McIntyre [this message]
2010-09-25 15:45     ` Kristaps Dzonsons
2010-09-25 17:47       ` Jason McIntyre
2010-09-25 20:18         ` Kristaps Dzonsons
2010-09-25 21:25           ` Jason McIntyre
2010-09-25 21:29             ` Kristaps Dzonsons
2010-09-25 21:38 ` Ingo Schwarze
2010-09-25 21:43   ` Joerg Sonnenberger

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=20100925153525.GD25298@bramka.kerhand.co.uk \
    --to=jmc@kerhand.co.uk \
    --cc=discuss@mdocml.bsd.lv \
    /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).