From: Michael Albinus <michael.albinus@gmx.de>
To: John Shahid <jvshahid@gmail.com>
Cc: 35506@debbugs.gnu.org
Subject: bug#35506: 27.0.50; Emacs hangs while interrupting tramp processes
Date: Fri, 03 May 2019 10:30:41 +0200 [thread overview]
Message-ID: <875zqs7xe6.fsf@gmx.de> (raw)
In-Reply-To: <87y33rzalc.fsf@gmail.com> (John Shahid's message of "Tue, 30 Apr 2019 13:06:39 -0400")
John Shahid <jvshahid@gmail.com> writes:
Hi John,
> It looks like the first issue can be solved by killing the entire
> process group, but I am not sure how safe it is to always do that. I
> will attach a patch that I use locally which seem harmless so far.
Reading the Emacs manual again at (info "(elisp) Signals to Processes")
--8<---------------cut here---------------start------------->8---
If CURRENT-GROUP is ‘nil’, the signal is sent to the process group of
the immediate subprocess of Emacs.
--8<---------------cut here---------------end--------------->8---
So your patch is correct, pls push.
> The second issue can be solved by not waiting for the process to exit.
> This seems to be in line with the contract of `interrupt-process'. I
> will attach a patch to remove the wait.
No, Tramp must report success. See the Emacs manual, same location as
above:
--8<---------------cut here---------------start------------->8---
-- Variable: interrupt-process-functions
This variable is a list of functions to be called for
‘interrupt-process’. The arguments of the functions are the same
as for ‘interrupt-process’. These functions are called in the
order of the list, until one of them returns non-‘nil’. The
default function, which shall always be the last in this list, is
‘internal-default-interrupt-process’.
This is the mechanism, how Tramp implements ‘interrupt-process’.
--8<---------------cut here---------------end--------------->8---
So we must investigate, why `interrupt-process' does not return in your case.
Best regards, Michael.
PS: In the FSF list, your email address is given as <vshahid@gmail.com>.
Looks like a typo, maybe you contact the FSF clerk about.
next prev parent reply other threads:[~2019-05-03 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 17:06 bug#35506: 27.0.50; Emacs hangs while interrupting tramp processes John Shahid
[not found] ` <handler.35506.B.155664402325068.ack@debbugs.gnu.org>
2019-04-30 17:28 ` bug#35506: Acknowledgement (27.0.50; Emacs hangs while interrupting tramp processes) John Shahid
2019-05-03 8:30 ` Michael Albinus [this message]
2019-05-04 14:33 ` bug#35506: 27.0.50; Emacs hangs while interrupting tramp processes John Shahid
2019-05-04 16:36 ` Michael Albinus
2019-05-04 17:44 ` John Shahid
2019-05-04 18:07 ` John Shahid
2019-05-14 18:19 ` Michael Albinus
2019-05-14 18:59 ` John Shahid
2019-05-15 14:32 ` 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=875zqs7xe6.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=35506@debbugs.gnu.org \
--cc=jvshahid@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).