From 4774a3abb4be3068e0308820c73b71c2a924fb21 Mon Sep 17 00:00:00 2001 From: Michael Albinus Date: Thu, 30 Nov 2023 14:37:40 +0100 Subject: [PATCH] Document, that PROCESS of signal-process can be a string * doc/lispref/processes.texi (Signals to Processes) [signal-process]: * src/process.c (Fsignal_process): Document, that PROCESS can be a string. --- doc/lispref/processes.texi | 3 +++ src/process.c | 2 ++ 2 files changed, 5 insertions(+) diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi index e1398749005..b3ba58ec643 100644 --- a/doc/lispref/processes.texi +++ b/doc/lispref/processes.texi @@ -1497,6 +1497,9 @@ If @var{process} is a process object which contains the property @code{remote-pid}, or @var{process} is a number and @var{remote} is a remote file name, @var{process} is interpreted as process on the respective remote host, which will be the process to signal. + +If @var{process} is a string, it is interpreted as process object with +the respective process name, or as a number. @end deffn Sometimes, it is necessary to send a signal to a non-local diff --git a/src/process.c b/src/process.c index 46e57c1a7c2..4ee742c6cef 100644 --- a/src/process.c +++ b/src/process.c @@ -7185,6 +7185,8 @@ If PROCESS is a process object which contains the property `remote-pid', or PROCESS is a number and REMOTE is a remote file name, PROCESS is interpreted as process on the respective remote host, which will be the process to signal. +If PROCESS is a string, it is interpreted as process object with the +respective process name, or as a number. SIGCODE may be an integer, or a symbol whose name is a signal name. */) (Lisp_Object process, Lisp_Object sigcode, Lisp_Object remote) { -- 2.39.2