From: "Anthony J. Bentley" <anthony@cathet.us>
To: discuss@mdocml.bsd.lv
Subject: Text embedded in Bl
Date: Sun, 22 Sep 2013 16:33:21 -0600 [thread overview]
Message-ID: <1490.1379889201@cathet.us> (raw)
Hi,
Consider the following, based on an example from gnugk(1):
.Bl -tag -width Ds
This is an opening paragraph.
.It Fl a
Perform behavior foo.
...
.El
Mandoc refuses to display the page:
FATAL: child violates parent syntax
Groff, on the other hand, displays it (I'm not sure of the specifics, but
my guess is it treats the first part as a Pp):
This is an opening paragraph.
-a Perform behavior foo.
To me, this is obviously wrong. To realize why, just think of the case
where you want two paragraphs. (Or the case where the Bl only contains a
single paragraph with no items--which also appeared in this manpage!)
Based on this reasoning, I sent a fixed manpage to upstream, who committed
it.
But now I wonder. Should mandoc mimic groff here? I think no, but maybe
someone else will have a different opinion.
--
Anthony J. Bentley
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2013-09-22 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 22:33 Anthony J. Bentley [this message]
2013-09-22 23:42 ` 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=1490.1379889201@cathet.us \
--to=anthony@cathet.us \
--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).