From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Thaddeus H . Black" <thb@debian.org>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
"G . Branden Robinson" <g.branden.robinson@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org
Subject: [PATCH] .P -> .PP
Date: Thu, 9 Sep 2021 09:28:53 +0200 [thread overview]
Message-ID: <20210909072853.423334-1-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210909072442.423117-4-alx.manpages@gmail.com>
And another trivial one you can squash.
---
man7/filename.7 | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/man7/filename.7 b/man7/filename.7
index 0e42e39d4..d60fe08eb 100644
--- a/man7/filename.7
+++ b/man7/filename.7
@@ -141,10 +141,10 @@ termination of options processing [see
but when reprocessing of shell-command text requires requotation and
re-escape, the workarounds become an inconvenient, confusing, error-prone
hassle.
-.P
+.PP
The use of conventional filenames averts the hassle.
It also makes filenames more recognizable to experienced users.
-.P
+.PP
This section introduces broadly observed conventions for filenames.
.TP
.B The POSIX Portable Filename Character Set
@@ -284,7 +284,7 @@ or
Further filenaming conventions are softer.
Though often observed, such softer conventions can be bent or broken
without rendering filenames unconventional.
-.P
+.PP
This section introduces soft conventions for filenames.
.TP
.B Low line versus hyphen-minus
@@ -409,7 +409,7 @@ Approximately, in brief, Unicode is a character set, UTF-8 is a
byte-oriented scheme by which Unicode characters can be encoded, and ASCII
is both a character set and a byte-oriented scheme that is a subset of both
Unicode and UTF-8.]
-.P
+.PP
To suggest an exact noninternational filenaming rule, other than the
.BR iswgraph (3)
rule, for every locale would exceed the scope of this manual page; but
@@ -421,7 +421,7 @@ exclude spaces, control characters, ASCII symbols (like\~\fB$\fR
or\~\fB=\fR), and ASCII punctuators other than the three punctuators POSIX
recommends, such filenames will not normally cause trouble for tools and,
thus, may be regarded as conventional within the local context.
-.P
+.PP
The use of nonbreaking spaces like\~\fB\eu00A0\fR, \fB\eu2007\fR,
\fB\eu202F\fR or\~\fB\euFEFF\fR in filenames is probably inadvisable for
most locales, despite that
@@ -447,9 +447,9 @@ You may have noticed the unconventionally-named
.I lost+found
directory lurking at a filesystem's root on your computer; and there are
further examples, as well.
-.P
+.PP
There are many reasons to use unconventional filenames.
-.P
+.PP
It is hard to give a general rule, with respect to a particular context, as
to which unconventional filenames are likely to cause practical troubles
and which are not.
@@ -514,7 +514,7 @@ POSIX.1-2008, SUSv4.
.BR locale (7),
.BR unicode (7),
.BR utf-8 (7)
-.P
+.PP
info
.B coreutils
.\" The author, Thaddeus H. Black, thanks his wife Kristie, daughter Naomi
--
2.33.0
next prev parent reply other threads:[~2021-09-09 7:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 11:40 [PATCH] filename.7: new manual page Thaddeus H. Black
2021-09-06 14:21 ` Alejandro Colomar (man-pages)
2021-09-06 16:59 ` G. Branden Robinson
2021-09-06 21:47 ` Alejandro Colomar (man-pages)
2021-09-08 3:54 ` G. Branden Robinson
2021-09-08 14:56 ` Thaddeus H. Black
2021-09-08 15:45 ` Alejandro Colomar (man-pages)
2021-09-09 2:15 ` Thaddeus H. Black
2021-09-09 2:45 ` Thaddeus H. Black
2021-09-09 7:24 ` [PATCH 1/3] Remove unnecessary .P after .S[HS] Alejandro Colomar
2021-09-09 7:24 ` [PATCH 2/3] Fix indentation of paragraph, which continues talking about \0 Alejandro Colomar
2021-09-09 7:24 ` [PATCH 3/3] Use subsections instead of sections Alejandro Colomar
2021-09-09 7:28 ` Alejandro Colomar [this message]
2021-09-12 14:20 ` Thaddeus H. Black
2021-09-12 14:49 ` Alejandro Colomar (man-pages)
2021-09-12 14:56 ` Alejandro Colomar (man-pages)
2021-09-12 15:22 ` Thaddeus H. Black
2021-09-12 18:49 ` G. Branden Robinson
2021-09-12 18:12 ` G. Branden Robinson
2021-09-12 22:39 ` Alejandro Colomar (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210909072853.423334-1-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=thb@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox