From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: docbook2mdoc: translate <paramdef> to .Fa even outside <funcprototype>
Date: Wed, 3 Apr 2019 10:24:56 -0500 (EST) [thread overview]
Message-ID: <e3fd33d40925dce0@fantadrom.bsd.lv> (raw)
Log Message:
-----------
translate <paramdef> to .Fa even outside <funcprototype>
Modified Files:
--------------
docbook2mdoc:
docbook2mdoc.c
Revision Data
-------------
Index: docbook2mdoc.c
===================================================================
RCS file: /home/cvs/mdocml/docbook2mdoc/docbook2mdoc.c,v
retrieving revision 1.86
retrieving revision 1.87
diff -Ldocbook2mdoc.c -Ldocbook2mdoc.c -u -p -r1.86 -r1.87
--- docbook2mdoc.c
+++ docbook2mdoc.c
@@ -766,6 +766,7 @@ pnode_print(struct format *p, struct pno
case NODE_PARA:
pnode_printpara(p, pn);
break;
+ case NODE_PARAMDEF:
case NODE_PARAMETER:
macro_nodeline(p, "Fa", pn, ARG_SINGLE);
pnode_unlinksub(pn);
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-04-03 15:24 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=e3fd33d40925dce0@fantadrom.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.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).