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: Mon, 27 Jun 2022 13:49:56 +0200 Message-ID: <877d52uxzv.fsf@gmx.de> References: <87edzb9mot.fsf@gnus.org> <87bkuev1qu.fsf@gmx.de> <87o7ye5qxy.fsf@gnus.org> <83ilom8i2c.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14962"; 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 Mon Jun 27 13:54:28 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 1o5nJz-0003c8-Vn for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 27 Jun 2022 13:54:28 +0200 Original-Received: from localhost ([::1]:57320 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o5nJy-00036g-RN for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 27 Jun 2022 07:54:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34030) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o5nGg-0006h8-Uq for bug-gnu-emacs@gnu.org; Mon, 27 Jun 2022 07:51:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56195) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o5nGg-0005IK-My for bug-gnu-emacs@gnu.org; Mon, 27 Jun 2022 07:51:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o5nGg-0002D9-KG for bug-gnu-emacs@gnu.org; Mon, 27 Jun 2022 07:51: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: Mon, 27 Jun 2022 11:51:02 +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.16563306088421 (code B ref 56239); Mon, 27 Jun 2022 11:51:02 +0000 Original-Received: (at 56239) by debbugs.gnu.org; 27 Jun 2022 11:50:08 +0000 Original-Received: from localhost ([127.0.0.1]:50092 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o5nFo-0002Bl-0K for submit@debbugs.gnu.org; Mon, 27 Jun 2022 07:50:08 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:42905) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o5nFk-0002B6-Mm for 56239@debbugs.gnu.org; Mon, 27 Jun 2022 07:50:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1656330597; bh=3dszv1r4jBAkfBquyZoxkgSJIEbkkdsA4aexD0exQSE=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=iQSbSr9m6ti+C8O40nEF8ekks4Wnsa6ns0Zct7KsuBfP24VgdABJ2AuSP0ISDe/Iw VQTexAgvsDF26fezsCUsdovhP8hhMNm7YkNGqtPAde+K9rc4d1MmN9qZ0DuTqOuNP4 D835UYu/2Sg8z/3XRLIR4KZKJDFaTDZC60QvfbiY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from gandalf.gmx.de ([213.220.151.145]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MPXhK-1oJb0x1o2M-00MciS; Mon, 27 Jun 2022 13:49:57 +0200 In-Reply-To: <83ilom8i2c.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 27 Jun 2022 14:24:59 +0300") X-Provags-ID: V03:K1:Uu8eiPSDJQdGr/wRTEsqF0iu4idc9Ad+6EgWx4MazQxqeaT9mK+ gVqxSn1h/xNKNIy5Z0jXaDjoV1h8t0ubFCvNQgE3EzoPNiw71w2/L9FRrrSBdXLAhtUdEy/ LcjLNQPdiqA2rrsn5hmeD6NM6V/iE65m2kQ4rYT9lx7zjC5G0YIZl52/k2hOPzUPyQmSr+C zuleGF7G8/X07+fJ7rFVg== X-UI-Out-Filterresults: notjunk:1;V03:K0:lWNEhOmhrlg=:vVgAyEIDUfsQH5vshkMLBD H8rUQ81yfFbLmoc+ZueNp+1AYEjq0CxId8Hb7VQkn3/dHM3oyIK9X7fSXM4369cYFphbIRMqw SOM3qitMlPfFtgVJ9JaVI0RSoSIXFRR9xVawv8VJMusPJIuskVUMPdkeRDjJgBRMtoyk9dy6V q87WQzyMivRoIrUMe4PrOnip6u2sYh1t1CcB1lbMAX1/qdTs09Va+/oH6d8nVqiFM/VsQau+0 6q7MGPXwBeQy0906demmopdZuDqPwyzAtxNcMn1tqsuF5ZpM5uRo8t+Istca7HuwJ+ehM0/r7 gfV4mwdo7sygqs4kR++Fbzyn0UOCNFHYr6MXYtA3czYc+VMqTV9uDP7PeaR/I/AKzZstPn/oq WVY/Xems3+Rfqj6W5HeKTjD1C1fFBSgMU3FaRrjtqNpz3N61ZmWwaq7MhbIR6wRHxdZ5F+3qw 6I1+/FZYorFBYri/uQlfN37qQDvI08RWrCc5dFp9xaM/KhVSqX6hK52cH80Wn7nzrlgOD7Vqa so+VfVo1eWTPjmlJvKLBRuqrErKmaACDe9wdMHAWx9IIu6SFmQ6z5zFyPz7mPLwOKf1uujy2u J8rnMjwvjhTz9YhVAM0fiPEow94I4x+AQgi8xPy/ITSvkypICQCzB3OBX6h18ZoivOelR2Xik KzmGnvwCIhWmNqEVpjW+Ood8i7WWespAMPV/PS5uVbKfnPpJlK6i8eFn3zooSgps/T6QWe6vV gJbNwnrabHBTUferO+dXSxcPyKX1r+NOn2c6Jt2K0qH+fa0UyXiMdxlHSeSsQp9XRMgId9OH 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:235438 Archived-At: Eli Zaretskii 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 tha= t >> > 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 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. Best regards, Michael.