From: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: define-key upon common-lisp-mode and inferior-lisp-mode
Date: Wed, 31 Aug 2022 14:04:50 +0200 [thread overview]
Message-ID: <87h71sr4wv.fsf@gmail.com> (raw)
In-Reply-To: <831qsxvo20.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Use local-set-key instead.
>
>> On the other modes I have been using
>>
>> (define-key emacs-lisp-mode-map (kbd "H-e") #'eval-last-sexp)
>>
>> The last seems more standard for many modes.
>
> I can only show you the better solutions, I cannot force you use them.
The documentation says local-set-key is legacy, and should be replaced
by keymap-local-set.
But aside from that, I only use define-key, and it works pretty good.
What are the advantages of using keymap-local-set? When using define-key
with the mode specific map, I'm not polluting other keymaps. So why the
need for a local function?
Alessandro
next prev parent reply other threads:[~2022-08-31 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:59 define-key upon common-lisp-mode and inferior-lisp-mode wilnerthomas--- via Users list for the GNU Emacs text editor
2022-08-30 11:44 ` Eli Zaretskii
2022-08-30 12:26 ` uzibalqa
2022-08-30 12:51 ` Eli Zaretskii
2022-08-30 13:22 ` uzibalqa
2022-08-30 13:49 ` Eli Zaretskii
2022-08-30 14:15 ` uzibalqa
2022-08-30 15:25 ` tomas
2022-08-30 18:21 ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-08-30 18:41 ` tomas
2022-08-30 19:08 ` wilnerthomas--- via Users list for the GNU Emacs text editor
2022-08-31 12:11 ` Alessandro Bertulli
2022-08-30 16:24 ` Eli Zaretskii
2022-08-31 12:04 ` Alessandro Bertulli [this message]
2022-08-31 12:42 ` Eli Zaretskii
2022-09-01 9:27 ` Alessandro Bertulli
2022-08-30 13:24 ` Stefan Monnier via Users list for the GNU Emacs text editor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h71sr4wv.fsf@gmail.com \
--to=alessandro.bertulli96@gmail.com \
--cc=eliz@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.