From de2f386bd8f978f415e5e800fcbd3fce8cd8b1cc Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Mon, 26 Nov 2018 17:44:34 +0000 Subject: 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. --- regress/roff/cond/close.out_ascii | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'regress/roff/cond/close.out_ascii') 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) -- cgit v1.2.3-56-ge451