From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 16312@debbugs.gnu.org
Subject: bug#16312: 24.3.50; Docstring fix for `set-transient-map' (and tangents...)
Date: Thu, 15 Jul 2021 07:18:50 +0200 [thread overview]
Message-ID: <87bl74qhmt.fsf@gnus.org> (raw)
In-Reply-To: <52C386FA.6040709@orcon.net.nz> (Phil Sainty's message of "Wed, 01 Jan 2014 16:09:46 +1300")
Phil Sainty <psainty@orcon.net.nz> writes:
> The docstring for `set-transient-map' states:
>
>> Note that MAP will take precedence over the \"overriding\" maps
>> `overriding-terminal-local-map' and `overriding-local-map' (and
>> over the `keymap' text property). Unlike those maps, if no match
>> for a key is found in MAP, Emacs continues the normal key lookup
>> sequence.
>
> The NEWS file suggests that this info is now incorrect for the
> former of those two:
>
>> * Incompatible Lisp Changes in Emacs 24.4
>>
>> ** `overriding-terminal-local-map' no longer replaces the local keymaps.
>> It used to disable the minor mode, major mode, and text-property keymaps,
>> whereas now it simply has higher precedence.
It seems like this was fixed in:
commit ec00f20f553cdd37c1261a5a228ec762fc9b5497
Author: Stefan Monnier <monnier@iro.umontreal.ca>
AuthorDate: Mon Jan 6 14:29:39 2014 -0500
> I also see the phrase "the keymap char property" in the docstring for
> `overriding-local-map'. Should that read "the keymap text property"? Or
> is this because there's a keymap Overlay property as well, and the
> `get-char-property' function checks them both?
Yup. I've now clarified this in the doc string in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-07-15 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55769.202.78.240.7.1388455781.squirrel@mail.orcon.net.nz>
2014-01-01 3:09 ` bug#16312: 24.3.50; Docstring fix for `set-transient-map' (and tangents...) Phil Sainty
2014-01-01 15:54 ` Drew Adams
2014-01-02 20:36 ` Phil Sainty
2021-07-15 5:18 ` Lars Ingebrigtsen [this message]
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=87bl74qhmt.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=16312@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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.