From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@linkov.net>
Cc: "James N. V. Cash" <james.nvc@gmail.com>, 42052@debbugs.gnu.org
Subject: bug#42052: 28.0.50; tab-bar-mode should be frame-local
Date: Sun, 12 Jul 2020 12:38:25 -0400 [thread overview]
Message-ID: <jwvpn907kqu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87d051zj14.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 12 Jul 2020 03:04:31 +0300")
Juri Linkov [2020-07-12 03:04:31] wrote:
>>> I don't know if such thing as frame-local keybindings is currently possible.
>>>
>>> The manual at (info "(elisp) Searching Keymaps") shows the decision tree:
>>
>> FWIW, I think it would be nice to eliminate the last few remaining
>> places where we collect the active keymaps by hand rather than by
>> calling Fcurrent_active_maps.
>>
>> Then we could allow Elisp code to modify the behavior of
>> `current-active-maps`.
>
> I can't find these places where the active keymaps are collected by hand.
Grep for `current_minor_maps`: it should ideally only be called from
Fcurrent_minor_mode_maps and Fcurrent_active_maps.
IIRC it's done in the code to build the menus and the tool bar.
Stefan
next prev parent reply other threads:[~2020-07-12 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 20:07 bug#42052: 28.0.50; tab-bar-mode should be frame-local James N. V. Cash
2020-06-27 23:40 ` Juri Linkov
2020-06-28 12:15 ` James N. V. Cash
2020-06-28 19:45 ` James N. V. Cash
2020-06-28 23:18 ` Juri Linkov
2020-06-29 0:26 ` James N. V. Cash
2020-06-29 0:35 ` James N. V. Cash
2020-06-29 23:45 ` Juri Linkov
2020-07-09 17:06 ` James N. V. Cash
2020-07-09 23:49 ` Juri Linkov
2020-07-11 14:45 ` James N. V. Cash
2020-07-12 0:01 ` Juri Linkov
2020-07-11 15:17 ` Stefan Monnier
2020-07-12 0:04 ` Juri Linkov
2020-07-12 16:38 ` Stefan Monnier [this message]
2020-10-13 3:07 ` Lars Ingebrigtsen
2021-01-05 18:36 ` Juri Linkov
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=jwvpn907kqu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=42052@debbugs.gnu.org \
--cc=james.nvc@gmail.com \
--cc=juri@linkov.net \
/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.