diff options
| author | Ingo Schwarze <schwarze@openbsd.org> | 2020-02-27 01:43:52 +0000 |
|---|---|---|
| committer | Ingo Schwarze <schwarze@openbsd.org> | 2020-02-27 01:43:52 +0000 |
| commit | 13c3ceece1e58741fca2635fed585eab72c2c298 (patch) | |
| tree | 5fef1cb532bff2686cae46fcbf801e02e138f255 /regress/mdoc/Sh/transp.in | |
| parent | d0fb47c4e52de4d83cd9b58fbfb7ef94c63ea96d (diff) | |
| download | mandoc-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/Sh/transp.in')
| -rw-r--r-- | regress/mdoc/Sh/transp.in | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/regress/mdoc/Sh/transp.in b/regress/mdoc/Sh/transp.in new file mode 100644 index 00000000..ef24d380 --- /dev/null +++ b/regress/mdoc/Sh/transp.in @@ -0,0 +1,11 @@ +.\" $OpenBSD: transp.in,v 1.1 2020/02/27 01:25:58 schwarze Exp $ +.Dd $Mdocdate$ +.Dt SH-TRANSP 1 +.Os +.Sh NAME +.Nm Sh-transp +.Nd interaction of sections with transparent nodes +.Sh DESCRIPTION +.Tg transparent +.Ss Subsection +text |