test whether the .Fl macro is parsed

3 files changed, 41 insertions, 3 deletions

diff --git a/regress/usr.bin/mandoc/mdoc/Fl/Makefile b/regress/usr.bin/mandoc/mdoc/Fl/Makefile
index 235122d1e9c..f0741596318 100644
--- a/regress/usr.bin/mandoc/mdoc/Fl/Makefile
+++ b/regress/usr.bin/mandoc/mdoc/Fl/Makefile
@@ -1,6 +1,10 @@
-# $OpenBSD: Makefile,v 1.3 2010/07/01 05:29:57 schwarze Exp $
+# $OpenBSD: Makefile,v 1.4 2011/01/01 22:08:43 schwarze Exp $
 
-REGRESS_TARGETS=noarg multiarg punct
-GROFF_TARGETS=noarg multiarg punct
+REGRESS_TARGETS=noarg multiarg parsed punct
+GROFF_TARGETS=noarg multiarg parsed
+
+# Do not regenerate the punct output file for now,
+# because groff-1.15 and groff-1.20.1 handle
+# the bar differently as a .Fl argument.
 
 .include <bsd.regress.mk>
diff --git a/regress/usr.bin/mandoc/mdoc/Fl/parsed.in b/regress/usr.bin/mandoc/mdoc/Fl/parsed.in
new file mode 100644
index 00000000000..ceb3706f782
--- /dev/null
+++ b/regress/usr.bin/mandoc/mdoc/Fl/parsed.in
@@ -0,0 +1,18 @@
+.Dd April 7, 2010
+.Dt FL-PARSED 1
+.Os
+.Sh NAME
+.Nm Fl-parsed
+.Nd is the Fl macro parsed?
+.Sh DESCRIPTION
+.Op Fl Ux
+.Pp
+.Op Ux
+.Pp
+.Op Fl Cm x
+.Pp
+.Fl W all
+versus
+.Fl W Ns Cm all
+.Pp
+.Fl Cm help
diff --git a/regress/usr.bin/mandoc/mdoc/Fl/parsed.out_ascii b/regress/usr.bin/mandoc/mdoc/Fl/parsed.out_ascii
new file mode 100644
index 00000000000..e9ccdc1540f
--- /dev/null
+++ b/regress/usr.bin/mandoc/mdoc/Fl/parsed.out_ascii
@@ -0,0 +1,16 @@
+FL-PARSED(1)               OpenBSD Reference Manual               FL-PARSED(1)
+
+NNAAMMEE
+     FFll--ppaarrsseedd - is the Fl macro parsed?
+
+DDEESSCCRRIIPPTTIIOONN
+     [--UNIX]
+
+     [UNIX]
+
+     [--xx]
+
+     --WW --aallll versus --WWaallll
+
+     --hheellpp
+