From: Michael Albinus <michael.albinus@gmx.de>
To: Duncan Greatwood <dgbulk@gmail.com>
Cc: 45518@debbugs.gnu.org
Subject: bug#45518: Ctrl-G Fails to Interrupt Hung Tramp Remote-Compile in Emacs 27.1
Date: Wed, 30 Dec 2020 11:36:30 +0100 [thread overview]
Message-ID: <87eej78tsh.fsf@gmx.de> (raw)
In-Reply-To: <CAN_Aq+py7nv+O+y-hRgcbbuzHohdYuB3pxEU=SWeSyw=PFjvyg@mail.gmail.com> (Duncan Greatwood's message of "Mon, 28 Dec 2020 17:10:58 -0800")
Duncan Greatwood <dgbulk@gmail.com> writes:
Hi Duncan,
> In emacs 26.2, Ctrl-G (usually ctrl-g three times) would interrupt the
> hung Tramp window, and indeed cause the errors to be displayed in the
> window as best as Tramp is able.
>
> In emacs 27.1, Ctrl-G does nothing in this
> "tramp-hung-while-compiling" situation. I also tried ctrl-c ctrl-c,
> but that also does nothing. It appears that the only way to kill the
> hung Tramp compile is to force-quit emacs as a whole at the OS level.
Well, in this area several changes have been applied since Emacs 27.1
has been released. Could you, pls, try the Tramp ELPA version (2.5.0)?
Even if it still blocks Emacs, there is a new option to write Tramp
traces to file. This would help us to find the culprit, if still
evident.
> Thanks as always.
> D.
Best regards, Michael.
next prev parent reply other threads:[~2020-12-30 10:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 1:10 bug#45518: Ctrl-G Fails to Interrupt Hung Tramp Remote-Compile in Emacs 27.1 Duncan Greatwood
2020-12-30 10:36 ` Michael Albinus [this message]
2020-12-30 21:13 ` Duncan Greatwood
2020-12-31 8:42 ` Michael Albinus
2021-01-03 10:27 ` Michael Albinus
2021-01-03 19:27 ` Duncan Greatwood
2021-01-06 13:37 ` Michael Albinus
2021-01-06 22:54 ` Duncan Greatwood
2021-01-11 10:58 ` Michael Albinus
2021-01-11 16:52 ` Duncan Greatwood
2021-01-11 17:56 ` Michael Albinus
2021-01-12 4:34 ` Duncan Greatwood
2021-01-12 9:02 ` Michael Albinus
2021-01-12 15:02 ` Michael Albinus
2021-01-29 5:15 ` Duncan Greatwood
2021-01-29 8:53 ` Michael Albinus
2021-02-10 15:40 ` Michael Albinus
2021-02-11 15:22 ` Michael Albinus
2021-02-14 1:38 ` Duncan Greatwood
2021-02-14 14:15 ` Michael Albinus
2021-02-15 20:21 ` Duncan Greatwood
2021-02-16 20:09 ` Michael Albinus
2021-02-17 5:41 ` Duncan Greatwood
2021-02-17 15:39 ` Michael Albinus
2021-03-16 1:36 ` Duncan Greatwood
2021-03-16 18:30 ` Michael Albinus
[not found] <CAN_Aq+rYcM7wHHWXKBqyY4P0Ew04RfkqnQUioqtUk0AOUeaRMA@mail.gmail.com>
2021-02-25 18:33 ` Michael Albinus
2021-03-15 20:49 ` Michael Albinus
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=87eej78tsh.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=45518@debbugs.gnu.org \
--cc=dgbulk@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).