From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Nested displays?
Date: Mon, 19 Jul 2010 19:09:25 +0200 [thread overview]
Message-ID: <20100719170925.GD11054@iris.usta.de> (raw)
In-Reply-To: <20100719120350.GI30454@bramka.kerhand.co.uk>
Hi Jason, hi Kristaps,
Jason McIntyre wrote on Mon, Jul 19, 2010 at 01:03:26PM +0100:
> On Mon, Jul 19, 2010 at 01:42:46PM +0200, Kristaps Dzonsons wrote:
>> Can anybody think of a reason why display types (`Bd', `D1', `Dl')
>> shouldn't be nested? Enclosed is a patch that downgrades the message
>> to ERROR (from FATAL) and lets these through.
> well, it doesn;t make sense to nest displays, does it? i can;t think of
> why you would ever want to. don;t tell me we have examples of this in
> our pages...
No longer:
From: Ingo Schwarze <schwarze@cvs.openbsd.org>
Date: Thu, 18 Feb 2010 06:39:21 -0700 (MST)
To: source-changes@cvs.openbsd.org
Subject: CVS: cvs.openbsd.org: src
CVSROOT: /cvs
Module name: src
Changes by: schwarze@cvs.openbsd.org 2010/02/18 06:39:21
Modified files:
share/man/man7 : mdoc.samples.7
share/man/man8 : intro.8
usr.bin/oldrdist: oldrdist.1
usr.sbin/openssl: openssl.1
Log message:
Our groff does not handle all cases of nested displays properly, so
resolve the contradiction in the manual whether it's allowed or not
in favour of "not allowed" for now, shelving my diff to support
nested displays in mandoc(1) for later consideration.
Found by and unbreaking the build with mandoc(1).
Feedback and OK jmc@
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-07-19 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 11:42 Kristaps Dzonsons
2010-07-19 12:03 ` Jason McIntyre
2010-07-19 13:37 ` Kristaps Dzonsons
2010-07-19 16:48 ` Joerg Sonnenberger
2010-07-19 17:09 ` 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=20100719170925.GD11054@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).