aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/regress/roff/cond/close.out_lint
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2018-11-26 17:44:34 +0000
committerIngo Schwarze <schwarze@openbsd.org>2018-11-26 17:44:34 +0000
commitde2f386bd8f978f415e5e800fcbd3fce8cd8b1cc (patch)
tree37a941b10f4129f199970613fca51164bc54dcc3 /regress/roff/cond/close.out_lint
parent9afc9f503996ea800d93d3aea67b2b9625c3ce9a (diff)
downloadmandoc-de2f386bd8f978f415e5e800fcbd3fce8cd8b1cc.tar.gz
mandoc-de2f386bd8f978f415e5e800fcbd3fce8cd8b1cc.tar.zst
mandoc-de2f386bd8f978f415e5e800fcbd3fce8cd8b1cc.zip
When a conditional block is closed by putting "\}" on a text line
by itself (which is somewhat unusual but not invalid; most authors use the empty macro line ".\}" instead), agree more closely with groff and do not produce a double space in the output. Quirk reported by millert@. While here, tweak the rest of the function body of roff_cond_text() to more closely match roff_cond_sub(). The subtly different handling could make people (including myself) wonder whether there is any point in being different. Testing shows there is not.
Diffstat (limited to 'regress/roff/cond/close.out_lint')
-rw-r--r--regress/roff/cond/close.out_lint4
1 files changed, 2 insertions, 2 deletions
diff --git a/regress/roff/cond/close.out_lint b/regress/roff/cond/close.out_lint
index 4387b057..d6f52146 100644
--- a/regress/roff/cond/close.out_lint
+++ b/regress/roff/cond/close.out_lint
@@ -1,2 +1,2 @@
-mandoc: close.in:15:2: ERROR: appending missing end of block: if
-mandoc: close.in:15:9: WARNING: skipping paragraph macro: sp after PP
+mandoc: close.in:31:2: ERROR: appending missing end of block: if
+mandoc: close.in:31:9: WARNING: skipping paragraph macro: sp after PP