From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: /usr/local/bin/emacs: writing to child signal FD: Bad file descriptor
Date: Sat, 04 Dec 2021 22:44:01 +0200 [thread overview]
Message-ID: <837dck5cdq.fsf@gnu.org> (raw)
In-Reply-To: <87h7bokswq.fsf@logand.com> (message from Tomas Hlavaty on Sat, 04 Dec 2021 21:37:57 +0100)
> From: Tomas Hlavaty <tom@logand.com>
> Date: Sat, 04 Dec 2021 21:37:57 +0100
>
> > What version of Emacs is that, and on what OS?
>
> GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27,
> cairo version 1.16.0)
You may wish trying the pretest of Emacs 28. Some problems in this
area were fixed after 27.2 was released, I think.
> > In general, typing C-g twice invokes "emergency exit", but that is
> > supposed to ask you a question before it ends the session.
>
> Mostly it does ask two questions iirc, save stuff? and then abort?
> But sometimes it crashes without questions.
The two questions it asks are the intended behavior. And if you tell
it to abort, then it does, and you may think it's a crash.
But it shouldn't crash without asking first.
> Is there some non-emergency way of interrupting blocking behaviour like
> network connections?
You can deliver a SIGUSR1 signal. But it doesn't necessarily help in
all situations.
next prev parent reply other threads:[~2021-12-04 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 1:12 /usr/local/bin/emacs: writing to child signal FD: Bad file descriptor Hongyi Zhao
2021-12-04 2:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-04 3:26 ` Hongyi Zhao
2021-12-04 3:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-04 12:05 ` Tomas Hlavaty
2021-12-04 12:16 ` Po Lu
2021-12-04 13:28 ` Eli Zaretskii
2021-12-04 20:37 ` Tomas Hlavaty
2021-12-04 20:44 ` Eli Zaretskii [this message]
2021-12-04 21:32 ` Tomas Hlavaty
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=837dck5cdq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).