From: Ingo Schwarze <schwarze@usta.de>
To: "Anthony J. Bentley" <anthony@cathet.us>
Cc: discuss@mdocml.bsd.lv
Subject: Re: groff/mandoc rendering difference with Lk
Date: Wed, 19 Nov 2014 19:02:46 +0100 [thread overview]
Message-ID: <20141119180246.GC28366@iris.usta.de> (raw)
In-Reply-To: <27703.1416387354@cathet.us>
Hi Anthony,
Anthony J. Bentley wrote on Wed, Nov 19, 2014 at 01:55:54AM -0700:
> .Sh SEE ALSO
> .Lk http://example.com/ The example homepage .
>
> This fragment renders as so in mandoc:
>
> SEE ALSO
> The example homepage: http://example.com/.
>
> But it renders like this in groff:
>
> SEE ALSO
> The: http://example.com/ example homepage.
>
> Unless this is a recent behavior change in groff (and thus a bug),
As far as i know, the .Lk macro is a groff addition.
Heirloom, for example, doesn't have it.
Similar macros taking free text arguments - An Cd Fd Mt Sx -
all accept an unlimited number of arguments, so .Lk should, too.
Only a few macros taking very special syntax elements as arguments
- Lb In St - limit their number of arguments in this way.
The odd behaviour of .Lk does not improve usability.
No one in their right mind would put the text following a macro
on the same line. Even if it works and the macro stops processing
arguments after a fixed number of arguments, it is much clearer
to put following text on the next line.
> mandoc should probably match the rendering so that mandoc users
> don't forget to quote the arguments.
This is one of the cases where i considered the behaviour of groff
so insane that i consciously chose to not follow. I think groff
should be fixed, i just didn't come round to do it.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2014-11-19 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 8:55 Anthony J. Bentley
2014-11-19 18:02 ` 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=20141119180246.GC28366@iris.usta.de \
--to=schwarze@usta.de \
--cc=anthony@cathet.us \
--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).