From: Gemini Lasswell <gazally@runbox.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 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 12:29:44 -0700 [thread overview]
Message-ID: <87o9djwt3r.fsf@runbox.com> (raw)
In-Reply-To: <87h8jb7qcs.fsf@gmx.de> (Michael Albinus's message of "Thu, 30 Aug 2018 18:48:19 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Appended is a first implementation. Comments?
I don't understand why this is so complicated. Why not just have the
thread show a message, instead of having it send a signal which gets
translated into an event that makes the main thread show a message?
Also, if we eventually implement one of the proposals in emacs-devel to
allow threads other than the main one to accept keyboard input, then
there would be no guarantee that putting the event in the keyboard
buffer would get it to the main thread.
next prev parent reply other threads:[~2018-08-30 19:29 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
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 [this message]
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=87o9djwt3r.fsf@runbox.com \
--to=gazally@runbox.com \
--cc=32502@debbugs.gnu.org \
--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).