From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 33510@debbugs.gnu.org
Subject: bug#33510: 26.1.90; M-x man crashes if invoking man fails
Date: Mon, 26 Nov 2018 19:18:48 +0200 [thread overview]
Message-ID: <834lc3iwp3.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58oi0MR-TokUA6sbxsrEh22wDrFdnRHZMv42EEMBGVYqnaw@mail.gmail.com> (message from Richard Copley on Mon, 26 Nov 2018 17:02:33 +0000)
[Please use Reply All to have the discussion recorded by the tracker.]
> From: Richard Copley <rcopley@gmail.com>
> Date: Mon, 26 Nov 2018 17:02:33 +0000
>
> On Mon, 26 Nov 2018 at 16:21, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Richard Copley <rcopley@gmail.com>
> > Date: Mon, 26 Nov 2018 12:34:41 +0000
> >
> > If invoking 'man' fails, M-x man crashes, with errors:
> > error in process sentinel: read-event: Buffer is read-only: #<buffer *Man xyzzy*>
> > error in process sentinel: Buffer is read-only: #<buffer *Man xyzzy*>
>
> Signaling an error is a far cry from a crash...
>
> Yes, sorry.
>
> > To reproduce from 'emacs -Q':
> > M-x man RET
> > xyzzy RET
>
> I cannot reproduce this, at least not on GNU/Linux: there, I get
>
> Can't find the xyzzy manpage
>
> as expected. On MS-Windows I get this instead:
>
> No manual entry for xyzzy.
>
> So I think the problem is triggered by something done by the 'man'
> port you have installed (an MSYS2 'man', perhaps?). What does it say
> if you invoke it from the shell prompt?
>
> There was no "man" on the path. (Sorry, I didn't realize that at the time.)
Ah, okay. With that, I _can_ reproduce the error.
next prev parent reply other threads:[~2018-11-26 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 12:34 bug#33510: 26.1.90; M-x man crashes if invoking man fails Richard Copley
2018-11-26 16:21 ` Eli Zaretskii
[not found] ` <CAPM58oi0MR-TokUA6sbxsrEh22wDrFdnRHZMv42EEMBGVYqnaw@mail.gmail.com>
2018-11-26 17:18 ` Eli Zaretskii [this message]
2018-12-01 9:31 ` Eli Zaretskii
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=834lc3iwp3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33510@debbugs.gnu.org \
--cc=rcopley@gmail.com \
/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).