From 13c3ceece1e58741fca2635fed585eab72c2c298 Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Thu, 27 Feb 2020 01:43:52 +0000 Subject: Introduce the concept of nodes that are semantically transparent: they are skipped when looking for previous or following high-level macros. Examples include roff(7) .ft, .ll, and .ta, mdoc(7) .Sm and .Tg, and man(7) .DT and .PD. Use this concept for a variety of improved decisions in various validators and formatters. While here, * remove a few const qualifiers on struct arguments that caused trouble; * get rid of some more Yoda notation in the vicinity; * and apply some other stylistic improvements in the vicinity. I found this class of issues while considering .Tg patches from kn@. --- regress/mdoc/Fl/spacing.out_markdown | 42 ++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 regress/mdoc/Fl/spacing.out_markdown (limited to 'regress/mdoc/Fl/spacing.out_markdown') diff --git a/regress/mdoc/Fl/spacing.out_markdown b/regress/mdoc/Fl/spacing.out_markdown new file mode 100644 index 00000000..a46a44e3 --- /dev/null +++ b/regress/mdoc/Fl/spacing.out_markdown @@ -0,0 +1,42 @@ +FL-SPACING(1) - General Commands Manual + +# NAME + +**Fl-spacing** - horizontal spacing after flag macros + +# DESCRIPTION + +with argument: +**-a** + +no next node: +**-** suffix + +transparent next node only: +**-** +suffix + +following text: +**-** +text + +text after transparent node on the same line: +**-** +text + +following macro on the same line: +**-**‌*word* + +following macro on the next line: +**-** +*word* + +following macro on the next line after transparent node on the same line: +**-** +*word* + +following macro after transparent node on the next line: +**-** +*word* + +OpenBSD - February 27, 2020 -- cgit