From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alexander Shukaev <emacs@Alexander.Shukaev.name>
Cc: 25189@debbugs.gnu.org
Subject: bug#25189: Use `current-global-map' in `comint-insert-input'
Date: Wed, 25 Dec 2019 22:39:51 +0100 [thread overview]
Message-ID: <874kxo3x08.fsf@gnus.org> (raw)
In-Reply-To: <40a05d64-0907-6b83-6961-dd4a2c510d31@Alexander.Shukaev.name> (Alexander Shukaev's message of "Wed, 25 Dec 2019 10:59:56 +0100")
Alexander Shukaev <emacs@Alexander.Shukaev.name> writes:
>> The value is a keymap that is usually (but not necessarily) Emacs’s
>> global map.
>
> So it's not necessarily the current global keymap. Hence, applying
> `define-key' (or any other mutating function to it), may not take any
> effect and do what is expected. It is safer to always use
> `current-global-map'. At least that is my understanding why there are
> special functions like `current-global-map' for accessing and
> `use-global-map' for assignment.
I'm unable to read any such thing from the documentation (or usage) of
those functions. A handful of places use use-global-map to alter what
global map is in usage, and I see no indication that functions like
comint-insert-input would want to alter these other maps instead of
(the real) global-map.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-12-25 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 0:36 bug#25189: Use `current-global-map' in `comint-insert-input' Alexander Shukaev
2019-07-27 11:29 ` Lars Ingebrigtsen
2019-12-16 1:58 ` Alexander Shukaev
[not found] ` <45ae521c-6f37-292e-c169-9ed591cb0504@Alexander.Shukaev.name>
2019-12-24 16:25 ` Lars Ingebrigtsen
2019-12-25 9:59 ` Alexander Shukaev
2019-12-25 21:39 ` Lars Ingebrigtsen [this message]
2019-12-26 0:32 ` Alexander Shukaev
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=874kxo3x08.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25189@debbugs.gnu.org \
--cc=emacs@Alexander.Shukaev.name \
/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).