From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: First, make `Pp' (next to `Sm') be allowed as the first element
Date: Wed, 22 Dec 2010 13:44:23 +0200 [thread overview]
Message-ID: <4D11E497.1080707@bsd.lv> (raw)
In-Reply-To: <20101222004323.GC9705@iris.usta.de>
> Here is what i have done in OpenBSD to fix this.
> Do you want that committed to bsd.lv as well?
>
> Apart from that, and from .TS, we are now back in full sync.
I don't suppose I mind this, but for completeness, would like a note in
mdoc.7 to the effect that `Sm' is allowed as a child of `Bl', as
"Lists consist of items started by the It macro..."
is erroneous. In general, I strongly want to avoid this sort of
sometimes-it's-ok ambiguity that groff so generously bestows. How about
a note after the list types saying that this is allowed?
Thanks,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-12-22 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201012160025.oBG0PZeE023827@krisdoz.my.domain>
2010-12-21 23:33 ` Ingo Schwarze
2010-12-22 0:43 ` Ingo Schwarze
2010-12-22 11:44 ` Kristaps Dzonsons [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=4D11E497.1080707@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).