tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
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 01:43:23 +0100	[thread overview]
Message-ID: <20101222004323.GC9705@iris.usta.de> (raw)
In-Reply-To: <20101221233338.GB9705@iris.usta.de>

Hi Kristaps,

replying to myself...

Ingo Schwarze wrote on Wed, Dec 22, 2010 at 12:33:38AM +0100:
> kristaps@mdocml.bsd.lv wrote on Wed, Dec 15, 2010 at 07:25:35PM -0500:

>> Log Message:
>> -----------
>> First, make `Pp' (next to `Sm') be allowed as the first element of a
>> `Bl' (before any `It' have been invoked).  Next, have the existence of
>> either macro raise a warning, as it's technically not legal according to
>> mdoc.7.

> Hmm, i agree it is good that Pp does not throw FATAL at this point,
> and it is good that Pp throws a WARNING here, but Sm is just fine.
[...]
> Note that it looks like Lp is missing, too.

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.

Yours,
  Ingo


--- /usr/mdocml/mdoc_validate.c	Sat Dec 18 12:03:18 2010
+++ ./mdoc_validate.c	Tue Dec 21 16:57:31 2010
@@ -1570,12 +1574,14 @@ post_bl(POST_ARGS)
 
 	for (n = mdoc->last->child; n; n = n->next) {
 		switch (n->tok) {
-		case (MDOC_It):
-			continue;
-		case (MDOC_Sm):
+		case (MDOC_Lp):
 			/* FALLTHROUGH */
 		case (MDOC_Pp):
 			mdoc_nmsg(mdoc, n, MANDOCERR_CHILD);
+			/* FALLTHROUGH */
+		case (MDOC_It):
+			/* FALLTHROUGH */
+		case (MDOC_Sm):
 			continue;
 		default:
 			break;
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-12-22  0:43 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 [this message]
2010-12-22 11:44     ` Kristaps Dzonsons

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=20101222004323.GC9705@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).