[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#32640: 26.1; Make `kill-process' a command

From: Phil Sainty
Subject: bug#32640: 26.1; Make `kill-process' a command
Date: Thu, 06 Sep 2018 15:03:35 +1200
User-agent: Orcon Webmail

On 2018-09-06 01:37, Michael Albinus wrote:
There's also `interrupt-process'. This has the additional feature to
send the SIGINT signal also to remote processes under Tramp control.

Is `interrupt-process' unique in this regard, Michael?

Checking "(elisp)Signals to Processes" shows me all of:

     -- Function: interrupt-process &optional process current-group
     -- Function: kill-process &optional process current-group
     -- Function: quit-process &optional process current-group
     -- Function: stop-process &optional process current-group
     -- Function: continue-process &optional process current-group
     -- Command: signal-process process signal

I feel that `kill-process' is more of a special case than the others
(to my mind it's more likely for a user to want to kill an inferior
process than to want to send one of the other signals; but maybe
that's just me?).  So personally I'm not fussed about making all of
these things commands; but it seems that all of those functions could
share common code for obtaining interactive arguments, so presumably
if it was done for one then it would be very straightforward to
convert the others as well if that was seen as beneficial.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]