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

[Lars Ingebrigtsen]

Phil Sainty <psainty@orcon.net.nz> writes:

> 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.

I've added your process prompting function to Emacs 29 (with some
trivial changes).  I think it makes sense to make kill-process into a
command (because I think that's a command people want to have), so I've
now done that.  The other ones -- I don't think there's much demand for
having those as commands, but if we want to, it's now trivial to do.

But I think we should wait to do so to see if anybody requests that, so
I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no