summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2019-04-30 11:48:10 +0000
committerIngo Schwarze <schwarze@openbsd.org>2019-04-30 11:48:10 +0000
commit43f9226f1dc68cb4e5298a723da0b838160b17ec (patch)
tree9e6f4723f62a2aad646638d5473e4bb0f775865a
parent120e720433c04ebfe7b465c35c0d9b0f95b3d0f8 (diff)
downloadmandoc-43f9226f1dc68cb4e5298a723da0b838160b17ec.tar.gz
improve the description of the message "blank line in fill mode";
triggered by a misunderstanding by sashan@
-rw-r--r--mandoc.15
1 files changed, 4 insertions, 1 deletions
diff --git a/mandoc.1 b/mandoc.1
index d29be7e9..5ecadffd 100644
--- a/mandoc.1
+++ b/mandoc.1
@@ -1699,9 +1699,12 @@ The meaning of blank input lines is only well-defined in non-fill mode:
In fill mode, line breaks of text input lines are not supposed to be
significant.
However, for compatibility with groff, blank lines in fill mode
-are replaced with
+are formatted like
.Ic \&sp
requests.
+To request a paragraph break, use
+.Ic \&Pp
+instead of a blank line.
.It Sy "tab in filled text"
.Pq mdoc , man
The meaning of tab characters is only well-defined in non-fill mode: