From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: ME macros: `i', `b', `r'
Date: Mon, 6 Dec 2010 22:43:26 +0100 [thread overview]
Message-ID: <20101206214326.GA12128@iris.usta.de> (raw)
In-Reply-To: <4CFCFDFD.8050201@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Mon, Dec 06, 2010 at 04:15:09PM +0100:
> In doing some clean-up, I noticed that the `i' and `b' macro don't
> actually do anything when invoked with `groff -Tascii -mandoc' or
> `nroff -mandoc'. Any arguments to the macros are unilaterally lost.
>
> This was tested on Debian testing (groff 1.20.1), NetBSD 5.0.1
> (1.19.2), and OpenBSD 4.6 (1.15).
>
> Seeing as this is the case, does anybody object to removing these
> macros to libroff and printing a warning when they're invoked?
Actually, i fail to find any uses in Xenocara or even ports.
OK, there is faces(1) in ports using .i at two places, which is
probably a typo, and then mairixrc(5), mimedefang-filter(5),
slapo-ppolicy(5) and lpd(8) using .b each once, and not a single
instance of .r.
Thus, why not just remove these three outright, such that they
hit the usual
MANDOCERR_MACRO, /* skipping unknown macro */
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-12-06 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:15 Kristaps Dzonsons
2010-12-06 21:43 ` Ingo Schwarze [this message]
2010-12-08 11:03 ` Kristaps Dzonsons
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=20101206214326.GA12128@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).