From: Christopher Yeleighton <giecrilj@stegny.2a.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: manuel@ledu-giraud.fr, 68583@debbugs.gnu.org
Subject: bug#68583: 29.1; Can't find the cat manpage
Date: Fri, 19 Jan 2024 12:17:08 +0000 [thread overview]
Message-ID: <3d80a687-9dd5-47fe-9758-4ca2c9ac3816@stegny.2a.pl> (raw)
In-Reply-To: <834jf9wmqv.fsf@gnu.org>
The error message is literally:
> Can't find the cat manpage
This is the title of this bug report, BTW ;-)
The right error message would be:
> Emacs cannot display the cat manpage, either because it cannot be
found or because it cannot be rendered. Try using the command ... to
diagnose the problem!
Troubleshooting instructions could be included in the mode documentation
instead.
On 19.01.2024 12:06, Eli Zaretskii wrote:
>> Date: Fri, 19 Jan 2024 12:05:03 +0000
>> Cc: manuel@ledu-giraud.fr, 68583@debbugs.gnu.org
>> From: Christopher Yeleighton <giecrilj@stegny.2a.pl>
>>
>> In that case, the error message emitted by Emacs is wrong. Emacs
>> assumes that the man process failed for a particular reason, which is
>> not the case.
> What is the error message, and why do you think it's wrong?
>
> What would be the right error message in this case?
next prev parent reply other threads:[~2024-01-19 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:06 bug#68583: 29.1; Can't find the cat manpage Christopher Yeleighton
2024-01-19 10:28 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 10:31 ` Christopher Yeleighton
2024-01-19 10:40 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 10:44 ` Christopher Yeleighton
2024-01-19 12:01 ` Eli Zaretskii
2024-01-19 12:05 ` Christopher Yeleighton
2024-01-19 12:06 ` Eli Zaretskii
2024-01-19 12:17 ` Christopher Yeleighton [this message]
2024-01-19 12:41 ` Eli Zaretskii
2024-01-19 12:46 ` Christopher Yeleighton
2024-01-19 14:32 ` Eli Zaretskii
2024-01-19 15:18 ` Christopher Yeleighton
2024-01-19 15:21 ` Christopher Yeleighton
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d80a687-9dd5-47fe-9758-4ca2c9ac3816@stegny.2a.pl \
--to=giecrilj@stegny.2a.pl \
--cc=68583@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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/emacs.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).