From: Tobias Geerinckx-Rice <me@tobias.gr>
To: 30785@debbugs.gnu.org
Subject: bug#30785: Man pages truncated, repeated
Date: Mon, 12 Mar 2018 22:24:46 +0100 [thread overview]
Message-ID: <4a0d5e493db8af05dd2292b854ad7d3d@tobias.gr> (raw)
Guix,
Perhaps he's just getting old, but our man has a tendency to forget
where he was, start over from the beginning, and repeat himself several
times:
$ guix package -i knot rofi
$ man 5 knot.conf | grep -E '^(NAME|DESCRIPTION)'
NAME
DESCRIPTION
NAME
DESCRIPTION
NAME
DESCRIPTION
NAME
DESCRIPTION
NAME
$
There's also some stderr...
<standard input>:25: error: end of file while defining macro
`UNINDENT'
...but I think that's just a symptom of the input being cut short; man
rofi(1) prints no such error yet suffers the same fate.
The affected man pages themselves are not truncated, nor do they repeat:
$ zgrep '\.SH' `man -w knot.conf`
.SH NAME
.SH DESCRIPTION
.SH COMMENTS
.SH INCLUDES
.SH MODULE SECTION
.SH SERVER SECTION
.SH KEY SECTION
.SH ACL SECTION
.SH CONTROL SECTION
.SH STATISTICS SECTION
.SH KEYSTORE SECTION
.SH SUBMISSION SECTION
.SH POLICY SECTION
.SH REMOTE SECTION
.SH TEMPLATE SECTION
.SH ZONE SECTION
.SH LOGGING SECTION
.SH AUTHOR
.SH COPYRIGHT
$
However, even longer man pages such as bash(1) render without fail, so
there might be something special about the two examples above that
triggers this behaviour.
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next reply other threads:[~2018-03-12 21:26 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 21:24 Tobias Geerinckx-Rice [this message]
2018-03-13 21:34 ` bug#30785: Man pages truncated, repeated Ludovic Courtès
2018-03-13 22:01 ` Tobias Geerinckx-Rice
2018-03-14 13:22 ` Ludovic Courtès
2018-03-14 13:43 ` Andreas Enge
2018-03-15 0:40 ` Marius Bakke
2018-05-05 21:40 ` Marius Bakke
2018-05-06 13:53 ` Marius Bakke
2018-05-06 22:06 ` Marius Bakke
2018-05-05 1:31 ` Vagrant Cascadian
2018-08-20 10:32 ` Pierre Neidhardt
2019-01-13 16:09 ` Pierre Neidhardt
2019-01-13 16:15 ` Pierre Neidhardt
2019-01-13 17:00 ` Ludovic Courtès
2019-01-13 17:31 ` Pierre Neidhardt
2019-01-13 17:43 ` Pierre Neidhardt
2019-01-13 20:27 ` Ludovic Courtès
2019-01-13 20:37 ` Pierre Neidhardt
2019-01-14 8:36 ` Ludovic Courtès
2019-01-14 8:49 ` Pierre Neidhardt
2019-01-14 10:19 ` Pierre Neidhardt
2019-01-14 10:59 ` Gábor Boskovits
2019-01-14 15:06 ` Pierre Neidhardt
2019-01-14 16:10 ` Ludovic Courtès
2019-01-14 16:24 ` Pierre Neidhardt
2019-01-14 16:42 ` Danny Milosavljevic
2019-01-14 16:57 ` Pierre Neidhardt
2019-01-14 17:46 ` Danny Milosavljevic
2019-01-14 17:48 ` Danny Milosavljevic
2019-01-14 17:50 ` Danny Milosavljevic
2019-01-14 18:19 ` Pierre Neidhardt
2019-01-14 20:27 ` Ludovic Courtès
2019-01-14 21:42 ` Danny Milosavljevic
2019-01-14 21:59 ` Pierre Neidhardt
2019-01-14 22:14 ` Danny Milosavljevic
2019-01-14 22:39 ` Pierre Neidhardt
2019-01-15 12:29 ` Ludovic Courtès
2019-01-16 10:01 ` Pierre Neidhardt
2019-01-16 10:56 ` Danny Milosavljevic
2019-01-16 13:02 ` Pierre Neidhardt
2019-01-16 14:17 ` Danny Milosavljevic
2019-01-16 17:39 ` Pierre Neidhardt
2019-01-16 18:12 ` Efraim Flashner
2019-01-16 18:18 ` Pierre Neidhardt
2019-01-16 19:57 ` Danny Milosavljevic
2019-01-16 22:32 ` Ludovic Courtès
2019-01-16 22:45 ` Danny Milosavljevic
2019-01-17 7:31 ` Pierre Neidhardt
2019-01-17 8:43 ` Ludovic Courtès
2019-01-17 9:39 ` Pierre Neidhardt
2019-01-17 9:42 ` Pierre Neidhardt
2019-01-17 11:32 ` Pierre Neidhardt
2019-11-28 0:13 ` Marius Bakke
2019-01-17 9:10 ` Danny Milosavljevic
2019-01-17 8:33 ` Ludovic Courtès
2019-01-17 8:41 ` Pierre Neidhardt
2021-04-22 18:53 ` G. Branden Robinson
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a0d5e493db8af05dd2292b854ad7d3d@tobias.gr \
--to=me@tobias.gr \
--cc=30785@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).