From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Fix previous such that all .It HEADs are unparsed, not just the
Date: Wed, 4 Jan 2012 19:43:52 -0500 (EST) [thread overview]
Message-ID: <201201050043.q050hqvV008888@krisdoz.my.domain> (raw)
Log Message:
-----------
Fix previous such that all .It HEADs are unparsed,
not just the first one in each -diag list.
While here, drop the needless if-statement
and choose a more precise wording for the comment.
ok kristaps@
Modified Files:
--------------
mdocml:
mdoc_macro.c
Revision Data
-------------
Index: mdoc_macro.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/mdoc_macro.c,v
retrieving revision 1.114
retrieving revision 1.115
diff -Lmdoc_macro.c -Lmdoc_macro.c -u -p -r1.114 -r1.115
--- mdoc_macro.c
+++ mdoc_macro.c
@@ -994,16 +994,6 @@ blk_full(MACRO_PROT_ARGS)
enum margverr av;
char *p;
- /*
- * Exception: `-diag' lists are not parsed, but lists in general
- * are parsed.
- */
- nparsed = 0;
- if (MDOC_It == tok && NULL != m->last &&
- MDOC_Bl == m->last->tok &&
- LIST_diag == m->last->norm->Bl.type)
- nparsed = 1;
-
nl = MDOC_NEWLINE & m->flags;
/* Close out prior implicit scope. */
@@ -1046,6 +1036,14 @@ blk_full(MACRO_PROT_ARGS)
return(0);
head = body = NULL;
+
+ /*
+ * Exception: Heads of `It' macros in `-diag' lists are not
+ * parsed, even though `It' macros in general are parsed.
+ */
+ nparsed = MDOC_It == tok &&
+ MDOC_Bl == m->last->parent->tok &&
+ LIST_diag == m->last->parent->norm->Bl.type;
/*
* The `Nd' macro has all arguments in its body: it's a hybrid
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2012-01-05 0:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201201050043.q050hqvV008888@krisdoz.my.domain \
--to=schwarze@mdocml.bsd.lv \
--cc=source@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).