summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKristaps Dzonsons <kristaps@bsd.lv>2009-07-12 19:34:51 +0000
committerKristaps Dzonsons <kristaps@bsd.lv>2009-07-12 19:34:51 +0000
commit38745750a7f599dc603af3810aca8ebb00c02e62 (patch)
treee98d660303c7b283b72d2b58d0576ab8da6a94ae
parenta2f621336638ee15b43b64a1332dd5fbea9b789d (diff)
downloadmandoc-38745750a7f599dc603af3810aca8ebb00c02e62.tar.gz
Fixed `Fo' superfluous space before `('. Noted groff compatibility in mdoc.7.
-rw-r--r--mdoc.75
-rw-r--r--mdoc_term.c3
2 files changed, 6 insertions, 2 deletions
diff --git a/mdoc.7 b/mdoc.7
index 919efe11..c3d92afb 100644
--- a/mdoc.7
+++ b/mdoc.7
@@ -580,6 +580,11 @@ If an special-character control character is escaped
.Sq \e\e ,
it will obviously not render the subsequent sequence. Even newer
versions of groff seem to dither on this.
+.\" LIST-ITEM
+.It
+In groff, the
+.Sq \&.Fo
+macro only produces the first parameter. This is no longer the case.
.El
.\" SECTION
.Sh SEE ALSO
diff --git a/mdoc_term.c b/mdoc_term.c
index 106cac04..285b21a9 100644
--- a/mdoc_term.c
+++ b/mdoc_term.c
@@ -1941,14 +1941,13 @@ termp_fo_pre(DECL_ARGS)
const struct mdoc_node *n;
if (MDOC_BODY == node->type) {
+ p->flags |= TERMP_NOSPACE;
term_word(p, "(");
p->flags |= TERMP_NOSPACE;
return(1);
} else if (MDOC_HEAD != node->type)
return(1);
- /* XXX - groff shows only first parameter */
-
p->flags |= ttypes[TTYPE_FUNC_NAME];
for (n = node->child; n; n = n->next) {
assert(MDOC_TEXT == n->type);