diff options
author | Ingo Schwarze <schwarze@openbsd.org> | 2018-11-26 17:44:34 +0000 |
---|---|---|
committer | Ingo Schwarze <schwarze@openbsd.org> | 2018-11-26 17:44:34 +0000 |
commit | de2f386bd8f978f415e5e800fcbd3fce8cd8b1cc (patch) | |
tree | 37a941b10f4129f199970613fca51164bc54dcc3 /regress/roff/cond/close.out_ascii | |
parent | 9afc9f503996ea800d93d3aea67b2b9625c3ce9a (diff) | |
download | mandoc-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_ascii')
-rw-r--r-- | regress/roff/cond/close.out_ascii | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/regress/roff/cond/close.out_ascii b/regress/roff/cond/close.out_ascii index 244d4154..d049154d 100644 --- a/regress/roff/cond/close.out_ascii +++ b/regress/roff/cond/close.out_ascii @@ -12,8 +12,18 @@ DDEESSCCRRIIPPTTIIOONN closing after plain text + conditional content following words with whitespace + + conditional contentfollowing words without whitespace + + preceding words standard multi-line style following words + + preceding words + + non-standard multi-line style following words + still open at the end of the file -OpenBSD 2013-06-27 COND-CLOSE(1) +OpenBSD November 26, 2018 COND-CLOSE(1) |