From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: remove .Xr spacing tweak
Date: Sat, 03 Dec 2011 22:44:25 +0100 [thread overview]
Message-ID: <4EDA9839.9050001@bsd.lv> (raw)
In-Reply-To: <20111203181634.GF17667@iris.usta.de>
On 03/12/2011 19:16, Ingo Schwarze wrote:
> Hi,
>
> i think it is time to remove an OpenBSD-specific tweak from the .Xr
> handling in OpenBSD mandoc(1) and make it compatible with bsd.lv
> mandoc and with groff-1.21.
> Right now, OpenBSD assumes an implicit .Ns after .Xr's second
> argument, if more non-punctuation arguments follow.
>
> This tweak in mdoc_macro.c was originally added for compatibility
> with groff-1.15, which is now gone for some time.
>
> The patch also scours the base tree, adapting those pages where
> the rendering would change.
Hi Ingo,
Of course this is fine by me -- the code is #ifdef'd in my repo anyway.
Does this warrant a COMPATIBILITY note, as it relates to old groff
behaviour?
Best,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-12-03 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 18:16 Ingo Schwarze
2011-12-03 21:44 ` Kristaps Dzonsons [this message]
2011-12-04 1:05 ` Ingo Schwarze
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=4EDA9839.9050001@bsd.lv \
--to=kristaps@bsd.lv \
--cc=tech@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).