From: Ingo Schwarze <schwarze@usta.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: MR macro (from GNU groff)
Date: Wed, 18 Oct 2023 23:31:48 +0200 [thread overview]
Message-ID: <ZTBOxCZAq3WSDEfX@asta-kit.de> (raw)
In-Reply-To: <ZTA7lPmdCFNCWQrK@debian>
Hi Alejandro,
Alejandro Colomar wrote on Wed, Oct 18, 2023 at 10:09:56PM +0200:
> As you know, I have plans to start using MR from GNU groff. But doing
> so without wide support from distros and formatters would be stupid.
[...]
> Do you have plans to add support for the MR macro?
Yes, it will be added. It shouldn't bee too difficult because it's
essentially a clone of mdoc(7) .Xr. Also, it is somewhat urgent
because the groff manual pages already use it, so i have to
support it in mandoc(1) before i can update the OpenBSD groff port
to 1.23.
The MF string register will be ignored, though. mandoc(1) will
always set the topic (or to use a more precise term, the *name*)
of the manual page linked to in the R font.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2023-10-18 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:09 Alejandro Colomar
2023-10-18 21:31 ` Ingo Schwarze [this message]
2023-10-18 21:54 ` Alejandro Colomar
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=ZTBOxCZAq3WSDEfX@asta-kit.de \
--to=schwarze@usta.de \
--cc=alx@kernel.org \
--cc=tech@mandoc.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).