summaryrefslogtreecommitdiffstats
path: root/regress/mdoc/Bd/spacing.in
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2020-02-27 01:43:52 +0000
committerIngo Schwarze <schwarze@openbsd.org>2020-02-27 01:43:52 +0000
commit13c3ceece1e58741fca2635fed585eab72c2c298 (patch)
tree5fef1cb532bff2686cae46fcbf801e02e138f255 /regress/mdoc/Bd/spacing.in
parentd0fb47c4e52de4d83cd9b58fbfb7ef94c63ea96d (diff)
downloadmandoc-13c3ceece1e58741fca2635fed585eab72c2c298.tar.gz
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@.
Diffstat (limited to 'regress/mdoc/Bd/spacing.in')
-rw-r--r--regress/mdoc/Bd/spacing.in8
1 files changed, 7 insertions, 1 deletions
diff --git a/regress/mdoc/Bd/spacing.in b/regress/mdoc/Bd/spacing.in
index 4b23da75..2346ebd7 100644
--- a/regress/mdoc/Bd/spacing.in
+++ b/regress/mdoc/Bd/spacing.in
@@ -1,4 +1,4 @@
-.\" $OpenBSD: spacing.in,v 1.3 2017/07/04 14:53:24 schwarze Exp $
+.\" $OpenBSD: spacing.in,v 1.4 2020/02/27 01:25:58 schwarze Exp $
.Dd $Mdocdate$
.Dt BD-SPACING 1
.Os
@@ -15,3 +15,9 @@ text between displays
compact display block
.Ed
following text
+.Sh EXAMPLES
+.Tg word
+.Bd -literal -offset indent
+text
+.Ed
+end of file