From: Eli Zaretskii <eliz@gnu.org>
To: Shynur Xie <one.last.kiss@outlook.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 65577@debbugs.gnu.org
Subject: bug#65577: 29.1; set <signal> <usr1> in global map
Date: Thu, 31 Aug 2023 13:03:52 +0300 [thread overview]
Message-ID: <83h6ofedfb.fsf@gnu.org> (raw)
In-Reply-To: <PH0PR11MB7470986B8590CB3C853AA963D7E0A@PH0PR11MB7470.namprd11.prod.outlook.com> (message from Shynur Xie on Mon, 28 Aug 2023 07:29:20 +0000)
> From: Shynur Xie <one.last.kiss@outlook.com>
> Date: Mon, 28 Aug 2023 07:29:20 +0000
> msip_labels:
>
> This report is about the question asked at
> <https://lists.gnu.org/archive/html/help-gnu-emacs/2023-08/msg00462.html>.
>
> Reproduce (-Q):
>
> (keymap-global-set "<signal> <usr1>"
> (lambda () ; doesn't work.
> (interactive)
> (message "teeest: signal usr1")))
> (signal-process (emacs-pid) 'sigusr1)
> (keymap-set special-event-map "<sigusr1>"
> (lambda () ; does work
> (interactive)
> (message "teeest: sigusr1")))
>
> Is this a documentation bug? Or am I missing something?
Stefan, it sounds like the first example is some left-over from old
handling of signals? I don't see a "function key" named 'signal'
bound anywhere in the global map. So the 1st example above should
only work if 'signal' is a prefix key bound in the global-map, right?
(keymap-lookup global-map "<f1>")
=> help-command
but
(keymap-lookup global-map "<signal>")
=> nil
next prev parent reply other threads:[~2023-08-31 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:29 bug#65577: 29.1; set <signal> <usr1> in global map Shynur Xie
2023-08-31 10:03 ` Eli Zaretskii [this message]
2023-08-31 12:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 7:39 ` Eli Zaretskii
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=83h6ofedfb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65577@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=one.last.kiss@outlook.com \
/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).