* Advise usage of \~ escape instead of \SPACE; the former, a groff extension from circa 1990, has been supported by Heirloom Doctools troff since 2005 and by mandoc since 2019. The advantage is that \~ is an _adjustable_ non-breaking space, so it will typeset non-jarringly both in .EX/.EE examples when filling is off, and in normal running text (which is filled). * Say "non-breaking" instead of "nonbreaking". These are the only occurrences of either in the man-pages tree, except in Changes.old, which uses "non-breaking". See linux-man@ list discussion at <https://lore.kernel.org/linux-man/\ 20210729115508.pt6btsqd7g5tuhg6@localhost.localdomain/> and follow-ups. --- man7/man-pages.7 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man7/man-pages.7 b/man7/man-pages.7 index 3819dfd97..06dc7097c 100644 --- a/man7/man-pages.7 +++ b/man7/man-pages.7 @@ -686,14 +686,14 @@ man 7 man\-pages If the command is short, then it can be included inline in the text, in italic format, for example, .IR "man 7 man-pages" . -In this case, it may be worth using nonbreaking spaces -("\e\ ") at suitable places in the command. +In this case, it may be worth using non-breaking spaces +(\e\(ti) at suitable places in the command. Command options should be written in italics (e.g., .IR \-l ). .PP Expressions, if not written on a separate indented line, should be specified in italics. -Again, the use of nonbreaking spaces may be appropriate +Again, the use of non-breaking spaces may be appropriate if the expression is inlined with normal text. .PP When showing example shell sessions, user input should be formatted in bold, for example -- 2.20.1
From 302aa3a0f2e5f0c3e9188936d4b0a25761ff5fd7 Mon Sep 17 00:00:00 2001 From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx> Date: Sat, 31 Jul 2021 13:30:58 +1000 Subject: [PATCH 2/2] man-pages.7: Update non-breaking space advice. * Advise usage of \~ escape instead of \SPACE; the former, a groff extension from circa 1990, has been supported by Heirloom Doctools troff since 2005 and by mandoc since 2019. The advantage is that \~ is an _adjustable_ non-breaking space, so it will typeset non-jarringly both in .EX/.EE examples when filling is off, and in normal running text (which is filled). * Say "non-breaking" instead of "nonbreaking". These are the only occurrences of either in the man-pages tree, except in Changes.old, which uses "non-breaking". See linux-man@ list discussion at <https://lore.kernel.org/linux-man/\ 20210729115508.pt6btsqd7g5tuhg6@localhost.localdomain/> and follow-ups. --- man7/man-pages.7 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man7/man-pages.7 b/man7/man-pages.7 index 3819dfd97..06dc7097c 100644 --- a/man7/man-pages.7 +++ b/man7/man-pages.7 @@ -686,14 +686,14 @@ man 7 man\-pages If the command is short, then it can be included inline in the text, in italic format, for example, .IR "man 7 man-pages" . -In this case, it may be worth using nonbreaking spaces -("\e\ ") at suitable places in the command. +In this case, it may be worth using non-breaking spaces +(\e\(ti) at suitable places in the command. Command options should be written in italics (e.g., .IR \-l ). .PP Expressions, if not written on a separate indented line, should be specified in italics. -Again, the use of nonbreaking spaces may be appropriate +Again, the use of non-breaking spaces may be appropriate if the expression is inlined with normal text. .PP When showing example shell sessions, user input should be formatted in bold, for example -- 2.20.1
Attachment:
signature.asc
Description: PGP signature
