From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.bugs Subject: bug#56239: 28.1; Cannot send signals by name to inferior process by calling signal-process interactively Date: Wed, 29 Jun 2022 15:34:57 +0200 Message-ID: <8735fnh9tq.fsf@gmx.de> References: <87edzb9mot.fsf@gnus.org> <87bkuev1qu.fsf@gmx.de> <87o7ye5qxy.fsf@gnus.org> <83ilom8i2c.fsf@gnu.org> <877d52uxzv.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26420"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Lars Ingebrigtsen , 56239@debbugs.gnu.org, mardani29@yahoo.es To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 29 16:25:45 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o6YdV-0006ie-FG for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Jun 2022 16:25:45 +0200 Original-Received: from localhost ([::1]:60792 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o6YdU-0005HU-Gx for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Jun 2022 10:25:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52224) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6XrT-00029W-LC for bug-gnu-emacs@gnu.org; Wed, 29 Jun 2022 09:36:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35991) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o6XrO-0008FH-3Z for bug-gnu-emacs@gnu.org; Wed, 29 Jun 2022 09:36:06 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o6XrO-000788-1V for bug-gnu-emacs@gnu.org; Wed, 29 Jun 2022 09:36:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Albinus Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 29 Jun 2022 13:36:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56239 X-GNU-PR-Package: emacs Original-Received: via spool by 56239-submit@debbugs.gnu.org id=B56239.165650971327320 (code B ref 56239); Wed, 29 Jun 2022 13:36:01 +0000 Original-Received: (at 56239) by debbugs.gnu.org; 29 Jun 2022 13:35:13 +0000 Original-Received: from localhost ([127.0.0.1]:58118 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o6Xqa-00076Z-N9 for submit@debbugs.gnu.org; Wed, 29 Jun 2022 09:35:13 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:37851) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o6XqV-00075z-2o for 56239@debbugs.gnu.org; Wed, 29 Jun 2022 09:35:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1656509699; bh=mzdbv7qP+fMK+5zW7LCeoaPKtvnpYvSep1Zol7RCFe4=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=AD3aA1S/TL4i31SNCYeRoYJxnAiI65TdWqGP1SGyZnjkZ1iW4dszS83oLaQBugwnA b3ZL1/Zms5JqZnW3u2wkSWwKetwOBhP7kdylfDBxobb/SgQs00Tf9C1X2becarnPrd PnX2XAbMISkVVrgB8LXnlz7AYGN7zNnnlvdQl/vw= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from gandalf.gmx.de ([79.140.124.34]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MIdeX-1nsX5y1zHh-00Ec7F; Wed, 29 Jun 2022 15:34:59 +0200 In-Reply-To: <877d52uxzv.fsf@gmx.de> (Michael Albinus's message of "Mon, 27 Jun 2022 13:49:56 +0200") X-Provags-ID: V03:K1:0A9bB9d5RTAa8ktz8MghAJ/Yo0x+6LTQq/s9ssBINRMRCU7l1vm Te7jeF19saz45Bux8k2qHq8dnGJvBR53UO7u675xZY8iWMgwzUOVXLIhByeOEGmD3Ctewkh naQ2/K/O859rDH1bNOjdb0rcSw7tED086rBDUfAQsYj/fADrQYUUbEcR2jU1L6MZDdmXB+k Fee1AgwuoX3HJaT2arYGg== X-UI-Out-Filterresults: notjunk:1;V03:K0:suzVY3jo3r4=:G1gR6JUWRtyKP56IpDmWiI HqWIGBy645Y4Oj8t1WPwZRKVdufbAnYp+R0E+lI3R9QnW568Io7D06I5UgArTxsigxSMriRaC OEp1PF1oSvcrspDE18CtukV9xsdYvWasyI872SU0cJeHviSLsAAYxk8sQHjgsBYFLVvyr92mM XIjpg/KWCYQYI5UPMGzdJQfbcZSeSxv05sBsfNOil31xkTsDHQelanCkJV939pKKSJsNxetai 8WdSOewaxruh/G2E4Ws9xqaG8X6JcYiQ1A1YC6Q8KhMXTLEpwaH8TJ/HGi+rkDvovfSkrQGKl Hb9WAVaNAx/VG13UCpCY+tBdMkmQCGQusPXnHwFlEB4I7zN/Rh1oMi8b6uSkV/9ForPaYGn0c xJ/9+U9sJ73mfH5r2zEb72LoJ2TapFcyd0ceDD0y6yxMWhy5Ovn5e64Med/u9miyI7ZOOMqzC e43Ab3RwkFaojtLpbK3oiDRZ/Gu6r53Lbwwsilp+4nht9a4ngpwfrX07xgJHDzabTOmQ6iuHK 4sX6nrLcFrPCurjOdxXeX3kNsgyCH3IdXI3LDk6yJVtZXICBGshyECPQgsRoQapNejanWY4cf NyhTuR+dFLRE9g9qlk6D6JnsTSzVqSxTT4vXgabdq/W/twLCbKQOaMLqrPygbShIBTbLNlf0E vbpoVOOtcZQQri/05Q0yKCtrqEyWsJWg1jCpmJIRpHDSNAmMLN+lTKY2y50ghRwlV7muZBiFO gSQaTlN0qi6a84S+BNBhZXp0kIyjNFYwQzhlLZVAl+X+hp9aDR+zT5qlO0Ke4unbn3dp6btJ X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:235638 Archived-At: Michael Albinus writes: > Hi, >>> > 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. >>> >>> I think users will just have to use numbers in those cases (which is >>> still possible). I.e., the symbol names are a convenience where it >>> works, but if not, then users can't use those. >> >> I agree, but there's a larger problem here: signal numbers that >> correspond to given names are also system-dependent. That is, SIGINT >> could be 2 on one system and 295 on another. So if you type >> >> M-x signal-process RET INT RET >> >> you could send to the process a signal number that will be interpreted >> on the remote host as some completely different signal. >> >> So I think we should at least document that symbolic names should be >> used for remote processes only very carefully, if at all. > > I don't mean to refrain from signal names. We have them already - Tramp > determines those names on the remote host when > process-file-return-signal-string is non-nil. The signal names are > returned when process-file returns with a retcode greater or equal 128. I've checked again - we don't send signals to remote hosts interactively. This would be posible only if the REMOTE argument of signal-process is non-nil. This doesn't happen interactively. Nothing to do ATM, therefore. > I like to use this existing mechanism also with signal-process. The > point is that signal-process (and interrupt-process) don't use the file > name handler mechanism, but an own implementation based on variables > signal-process-functions and interrupt-process-functions. This I would > like to move to the default file name handler implementation, which > would include a solution for signal names. This is a different topic, so we shouldn't discuss it here. Best regards, Michael.