From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: .IP without line args is not an ERROR
Date: Wed, 27 Oct 2010 22:46:11 +0200 [thread overview]
Message-ID: <20101027204611.GK16057@iris.usta.de> (raw)
In-Reply-To: <20101027124337.GA22794@britannica.bec.de>
Hi Joerg,
Joerg Sonnenberger wrote on Wed, Oct 27, 2010 at 02:43:37PM +0200:
> On Wed, Oct 27, 2010 at 12:22:24PM +0200, Ingo Schwarze wrote:
>> OK to commit this to bsd.lv, too?
> Are you sure that the handling is correct?
You mean, in man_term.c, (pre|post)_?P()?
I have not systematically tested all the cases, but i have read the
code, and it looks sane. Besides, there are comments indicating
that Kristaps had this in mind when writing the code (e.g. in the
definition of struct mtermp). I see no indication that anything
might be broken in that respect. Those cases i looked at, work.
Besides, that would be a wholly seperate issue. We are talking about
removing a non-fatal error in the parser. The resulting AST has
always been rendered in some way. Whether that rendering has issues
has nothing to do with the validity of the input.
> E.g. the "restore previous" behavior for missing arguments?
Actually, in that respect, man(7) is different than mdoc(7).
In mdoc, blocks can nest, but in man, if i understand correctly,
each block terminates the previous block, at least among the *P
blocks discussed here. Thus, the values in mtermp need no
resetting at all, and those in termp just get reset to mt->offset
and to the maximum right margin, no matter what the arguments
of the block were.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-10-27 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 10:22 Ingo Schwarze
2010-10-27 12:43 ` Joerg Sonnenberger
2010-10-27 20:46 ` Ingo Schwarze [this message]
2010-10-27 20:49 ` Joerg Sonnenberger
2010-10-27 20:58 ` 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=20101027204611.GK16057@iris.usta.de \
--to=schwarze@usta.de \
--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).