From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Wrong treatment of ".Nm ."
Date: Sat, 11 Jun 2011 17:46:03 +0200 [thread overview]
Message-ID: <20110611154603.GH4597@iris.usta.de> (raw)
In-Reply-To: <20110602093335.GP1002@acme.spoerlein.net>
Hi Ulrich,
Ulrich Spörlein wrote on Thu, Jun 02, 2011 at 11:33:35AM +0200:
>> .Sh SYNOPSIS
[...]
>> .Pp
>> .Nm rdump
>> is an alternate name for
>> .Nm .
[...]
> Usage of the
> .Ns Nm
> utility:
You are right, these are subtle mandoc bugs, i have added a TODO entry:
- When there is free text in the SYNOPSIS and that free text contains
the .Nm macro, groff somehow understands to treat the .Nm as an in-line
macro, while mandoc treats it as a block macro and breaks the line.
No idea how the logic for distinguishing in-line and block instances
should be, needs investigation.
uqs@ Thu, 2 Jun 2011 11:03:51 +0200
uqs@ Thu, 2 Jun 2011 11:33:35 +0200
Free text in the SYNOPSIS is perhaps not very good style,
but that's no reason for mandoc to behave differently.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-06-11 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:03 Ulrich Spörlein
2011-06-02 9:33 ` Ulrich Spörlein
2011-06-11 15:46 ` Ingo Schwarze [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=20110611154603.GH4597@iris.usta.de \
--to=schwarze@usta.de \
--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).