From: kristaps@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: pod2mdoc: Translate leading #include statements in verbatim SYNOPSIS
Date: Thu, 3 Apr 2014 12:50:32 -0400 (EDT) [thread overview]
Message-ID: <201404031650.s33GoWa2010643@krisdoz.my.domain> (raw)
Log Message:
-----------
Translate leading #include statements in verbatim SYNOPSIS text as In.
Modified Files:
--------------
pod2mdoc:
pod2mdoc.1
pod2mdoc.c
Revision Data
-------------
Index: pod2mdoc.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/pod2mdoc/pod2mdoc.c,v
retrieving revision 1.21
retrieving revision 1.22
diff -Lpod2mdoc.c -Lpod2mdoc.c -u -p -r1.21 -r1.22
--- pod2mdoc.c
+++ pod2mdoc.c
@@ -850,10 +850,47 @@ static void
verbatim(struct state *st, const char *buf, size_t start, size_t end)
{
int last;
+ size_t i;
if ( ! st->parsing || st->paused)
return;
-
+again:
+ /*
+ * If we're in the SYNOPSIS, see if we're an #include block.
+ * If we are, then print the "In" macro and re-loop.
+ * This handles any number of inclusions, but only when they
+ * come before the remaining parts...
+ */
+ if (SECT_SYNOPSIS == st->sect) {
+ i = start;
+ for (i = start; i < end && ' ' == buf[i]; i++)
+ /* Spin. */ ;
+ if (i == end)
+ return;
+ /* We're an include block! */
+ if (end - i > 10 &&
+ 0 == memcmp(&buf[i], "#include <", 10)) {
+ start = i + 10;
+ while (start < end && ' ' == buf[start])
+ start++;
+ fputs(".In ", stdout);
+ /* Stop til the '>' marker or we hit eoln. */
+ while (start < end &&
+ '>' != buf[start] && '\n' != buf[start])
+ putchar(buf[start++]);
+ putchar('\n');
+ if (start < end && '>' == buf[start])
+ start++;
+ if (start < end && '\n' == buf[start])
+ start++;
+ if (start < end)
+ goto again;
+ return;
+ }
+ }
+
+ if (start == end)
+ return;
puts(".Bd -literal");
for (last = ' '; start < end; start++) {
/*
Index: pod2mdoc.1
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/pod2mdoc/pod2mdoc.1,v
retrieving revision 1.11
retrieving revision 1.12
diff -Lpod2mdoc.1 -Lpod2mdoc.1 -u -p -r1.11 -r1.12
--- pod2mdoc.1
+++ pod2mdoc.1
@@ -101,6 +101,12 @@ Specifically, within each paragraph of t
following occur:
.Bl -bullet
.It
+If any number of
+.Li #include <foo.h>
+lines are found at the start of a verbatim paragraph, they're rendered
+with
+.Sq \&In .
+.It
An initial
.Li B<>
format code is rendered as
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2014-04-03 16:50 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=201404031650.s33GoWa2010643@krisdoz.my.domain \
--to=kristaps@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).