From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: util-linux@vger.kernel.org
Subject: [PATCH] doc: login-utils/*: Fix some warnings from "mandoc -T lint"
Date: Wed, 10 Jun 2020 22:49:59 +0000 [thread overview]
Message-ID: <20200610224959.GA21138@rhi.hi.is> (raw)
mandoc: ./login-utils/chfn.1:96:2: WARNING: skipping paragraph macro: PP empty
mandoc: ./login-utils/lslogins.1:14:2: WARNING: skipping paragraph macro: PP after SH
mandoc: ./login-utils/newgrp.1:18:2: WARNING: skipping paragraph macro: PP empty
mandoc: ./login-utils/nologin.8:19:2: WARNING: skipping paragraph macro: PP empty
mandoc: ./login-utils/sulogin.8:57:2: WARNING: skipping paragraph macro: PP empty
mandoc: ./login-utils/utmpdump.1:61:2: WARNING: skipping paragraph macro: PP after SS
mandoc: ./login-utils/vipw.8:65:2: WARNING: line scope broken: TP breaks I
####
There is no change in output from "nroff" or "groff".
Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
---
login-utils/chfn.1 | 1 -
login-utils/lslogins.1 | 1 -
login-utils/newgrp.1 | 1 -
login-utils/nologin.8 | 1 -
login-utils/sulogin.8 | 1 -
login-utils/utmpdump.1 | 1 -
login-utils/vipw.8 | 1 -
7 files changed, 7 deletions(-)
diff --git a/login-utils/chfn.1 b/login-utils/chfn.1
index 23f048325..9e4569622 100644
--- a/login-utils/chfn.1
+++ b/login-utils/chfn.1
@@ -93,7 +93,6 @@ r = Office (room), w = Office (work) Phone, h = Home Phone. For example,
If CHFN_RESTRICT is undefined, then all finger information is read-only.
This is the default.
.RE
-.PP
.SH EXIT STATUS
Returns 0 if operation was successful, 1 if operation failed or command syntax was not valid.
.SH AUTHORS
diff --git a/login-utils/lslogins.1 b/login-utils/lslogins.1
index 123f61ccf..6824001d4 100644
--- a/login-utils/lslogins.1
+++ b/login-utils/lslogins.1
@@ -11,7 +11,6 @@ lslogins \- display information about known users in the system
.RB [ \-l " \fIlogins\fR]"
.RI [ username ]
.SH DESCRIPTION
-.PP
Examine the wtmp and btmp logs, /etc/shadow (if necessary) and /etc/passwd
and output the desired data.
diff --git a/login-utils/newgrp.1 b/login-utils/newgrp.1
index 9902cd547..dc89b3cc2 100644
--- a/login-utils/newgrp.1
+++ b/login-utils/newgrp.1
@@ -15,7 +15,6 @@ is unchanged, but calculations of access permissions to files are performed
with respect to the new group ID.
.LP
If no group is specified, the GID is changed to the login GID.
-.LP
.SH FILES
.I /etc/group
.br
diff --git a/login-utils/nologin.8 b/login-utils/nologin.8
index 6fc6fc68f..a95ff2ba1 100644
--- a/login-utils/nologin.8
+++ b/login-utils/nologin.8
@@ -16,7 +16,6 @@ user instead of the default message.
The exit status returned by
.B nologin
is always 1.
-.PP
.SH OPTIONS
\fB\-c\fR, \fB\-\-command\fR \fIcommand\fR
.br
diff --git a/login-utils/sulogin.8 b/login-utils/sulogin.8
index 7e77cd541..0ba003ad3 100644
--- a/login-utils/sulogin.8
+++ b/login-utils/sulogin.8
@@ -54,7 +54,6 @@ to get the password. If these files are damaged or nonexistent, or when
root account is locked by '!' or '*' at the begin of the password then
.B sulogin
will \fBstart a root shell without asking for a password\fP.
-.PP
.IP
Only use the
.B \-e
diff --git a/login-utils/utmpdump.1 b/login-utils/utmpdump.1
index 4085f1760..c11a28fcc 100644
--- a/login-utils/utmpdump.1
+++ b/login-utils/utmpdump.1
@@ -58,7 +58,6 @@ But be warned,
.B utmpdump
was written for debugging purposes only.
.SS File formats
-.PP
Only the binary version of the
.BR utmp (5)
is standardised. Textual dumps may become incompatible in future.
diff --git a/login-utils/vipw.8 b/login-utils/vipw.8
index 6f9695ae4..e3d9eebf0 100644
--- a/login-utils/vipw.8
+++ b/login-utils/vipw.8
@@ -62,7 +62,6 @@ If the following environment variable exists, it will be utilized by
.B vipw
and
.BR vigr :
-.I
.TP
.B EDITOR
The editor specified by the string
--
2.26.2
reply other threads:[~2020-06-10 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200610224959.GA21138@rhi.hi.is \
--to=bjarniig@rhi.hi.is \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).