unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56239@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#56239: 28.1; Cannot send signals by name to inferior process by calling signal-process interactively
Date: Mon, 27 Jun 2022 12:28:57 +0200	[thread overview]
Message-ID: <87bkuev1qu.fsf@gmx.de> (raw)
In-Reply-To: <87edzb9mot.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 26 Jun 2022 22:47:30 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

Hi Lars,

>> For the signal code, type 'SIGUSR1 (or "SIGUSR1", or SIGUSR1).
>>
>> The operation fails with the message "Please enter a number".
>
> Yup.  I've now fixed this in Emacs 29.  I wasn't sure whether to allow
> completing to USR1 og SIGUSR1, and went with the former, but I don't
> really have an opinion on what form to use.  (So feel free to change
> that.)

Unfortunately, it's not such simple. signal-process can also deliver a
signal to a process running on a remote host. The signal names on that
host might differ from the signal names on the local host, collected by
Fsignal_names.

How do we want to handle this? I don't see a simple solution, because
the file name handler machinery is not in use here.

Best regards, Michael.





  reply	other threads:[~2022-06-27 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1tu8789mt.fsf.ref@yahoo.es>
2022-06-26 20:14 ` bug#56239: 28.1; Cannot send signals by name to inferior process by calling signal-process interactively Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-26 20:47   ` Lars Ingebrigtsen
2022-06-27 10:28     ` Michael Albinus [this message]
2022-06-27 10:41       ` Lars Ingebrigtsen
2022-06-27 11:24         ` Eli Zaretskii
2022-06-27 11:49           ` Michael Albinus
2022-06-29 13:34             ` 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=87bkuev1qu.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=56239@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mardani29@yahoo.es \
    /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).