From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: gazally@runbox.com, 32502@debbugs.gnu.org
Subject: bug#32502: 27.0.50; Tramp; C-g during asynchronous remote find-file kills Emacs
Date: Thu, 30 Aug 2018 16:18:59 +0300 [thread overview]
Message-ID: <83va7s0z7g.fsf@gnu.org> (raw)
In-Reply-To: <87zhx4wcsp.fsf@gmx.de> (message from Michael Albinus on Thu, 30 Aug 2018 09:09:42 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: gazally@runbox.com, 32502@debbugs.gnu.org
> Date: Thu, 30 Aug 2018 09:09:42 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> So it looks like you are right: we cannot send signals to the main
> >> thread. Is this acceptable?
> >
> > Yes, I think so, but let's document that.
>
> Sounds to me like a serious restriction. When something happens in a
> thread, I want to know it. There isn't even a message about the error.
If we want to announce the errors to the main thread, we can use
methods other than signaling an error. For example, we could inject
a special event into the input queue, similarly to how we produce
help-echo and other special events.
Fsignal is a very blunt weapon, its main effect is to throw to top
level. Why would we want to do that _in_the_main_thread_ when the
problem happened in another thread? That's disruptive, and could even
mean that the user will lose their edits. Not nice, IMO.
next prev parent reply other threads:[~2018-08-30 13:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 18:19 bug#32502: 27.0.50; Tramp; C-g during asynchronous remote find-file kills Emacs Gemini Lasswell
2018-08-22 18:46 ` Eli Zaretskii
2018-08-22 19:08 ` Eli Zaretskii
2018-08-22 19:23 ` Michael Albinus
2018-08-25 10:53 ` Michael Albinus
2018-08-25 12:42 ` Eli Zaretskii
2018-08-25 15:52 ` Michael Albinus
2018-08-25 16:07 ` Eli Zaretskii
2018-08-26 13:50 ` Gemini Lasswell
2018-08-30 9:24 ` Michael Albinus
2018-08-30 13:23 ` Eli Zaretskii
2018-08-30 13:28 ` Michael Albinus
2018-08-25 21:53 ` Gemini Lasswell
2018-08-26 14:12 ` Eli Zaretskii
2018-08-30 7:19 ` Michael Albinus
2018-08-30 12:34 ` Michael Albinus
2018-08-29 16:01 ` Michael Albinus
2018-08-29 16:23 ` Eli Zaretskii
2018-08-29 16:46 ` Michael Albinus
2018-08-29 17:03 ` Eli Zaretskii
2018-08-29 17:15 ` Michael Albinus
2018-08-29 20:22 ` Michael Albinus
2018-08-29 20:57 ` Michael Albinus
2018-08-30 2:36 ` Eli Zaretskii
2018-08-30 7:09 ` Michael Albinus
2018-08-30 13:18 ` Eli Zaretskii [this message]
2018-08-30 13:32 ` Michael Albinus
2018-08-30 13:51 ` Eli Zaretskii
2018-08-30 13:59 ` Michael Albinus
2018-08-30 16:48 ` Michael Albinus
2018-08-30 17:44 ` Eli Zaretskii
2018-08-30 19:30 ` Michael Albinus
2018-09-02 17:58 ` Michael Albinus
2018-09-02 20:03 ` Gemini Lasswell
2018-09-02 20:50 ` Michael Albinus
2018-08-30 19:29 ` Gemini Lasswell
2018-08-30 19:37 ` Michael Albinus
2018-08-31 6:52 ` Eli Zaretskii
2018-08-31 15:07 ` Gemini Lasswell
2018-08-31 17:45 ` Eli Zaretskii
2018-08-22 21:12 ` Gemini Lasswell
2018-08-23 14:01 ` 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=83va7s0z7g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32502@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=michael.albinus@gmx.de \
/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).