From: Shynur Xie <one.last.kiss@outlook.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: in which keymap to set SIGUSR-handler
Date: Sun, 27 Aug 2023 16:54:25 +0000 [thread overview]
Message-ID: <PH0PR11MB747073374051C5BAA2AA0614D7E1A@PH0PR11MB7470.namprd11.prod.outlook.com> (raw)
Hi, friends. I'm reading the elisp manual. In 22.7.12 Miscellaneous
System Events
(<https://gnu.org/s/emacs/manual/html_node/elisp/Misc-Events.html>),
there's a sample code about SIGUSR:
(keymap-set special-event-map "<sigusr1>" 'sigusr-handler)
In 22.7.13 Event Examples
(<https://gnu.org/s/emacs/manual/html_node/elisp/Event-Examples.html>)
there's another one:
(keymap-global-set "<signal> <usr1>" 'usr1-handler)
Which one should I use in my init file? Thanks in advance.
next reply other threads:[~2023-08-27 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 16:54 Shynur Xie [this message]
2023-08-27 17:59 ` in which keymap to set SIGUSR-handler Eli Zaretskii
2023-08-27 21:44 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2023-08-27 18:18 Shynur Xie
2023-08-27 18:50 ` 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=PH0PR11MB747073374051C5BAA2AA0614D7E1A@PH0PR11MB7470.namprd11.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).