From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Add -other-{window, frame} variants of project-prefix-map commands
Date: Thu, 09 Jul 2020 03:24:30 +0300 [thread overview]
Message-ID: <87r1tl358h.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvd056y7vm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 08 Jul 2020 00:06:34 -0400")
> Note also that the tension between parsing `C-x 4 FOO` as "lookup FOO in
> `ctl-x-4-map` (or in `ofw-transient-map`)" and "lookup FOO in the normal
> way", which is why in `ofw--set-prefix` we do:
>
> ;; FIXME: Setup a transient map to reproduce the behavior of the `C-x 4/5'
> ;; prefix keys, but only do it in "regular" buffers. In special buffers,
> ;; these extra bindings may be more annoying than anything, e.g. in Gnus's
> ;; summary buffer `a' open a new message buffer, so we'd want `C-x
> ;; 5 a' to open it in a new frame, but instead of calling
> ;; add-change-log-entry.
The latter ("lookup FOO in the normal way") is handled now by `C-x 5 5 a`,
so the transient map for the former ("lookup FOO in `ctl-x-4-map`")
could contain only cherry-picked shorthands to reduce longer key sequences
like `C-x 5 5 C-x C-f` to just `C-x 5 f`.
Maybe even it could employ some heuristic to automatically deduce
the transient map based on the existing `C-x` keymap. For example,
from `C-x p b` (project-switch-to-buffer) it could build a new key
sequence `C-x 5 p b`, etc. This could help to close bug#42210.
next prev parent reply other threads:[~2020-07-09 0:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 0:54 Add -other-{window,frame} variants of project-prefix-map commands Sean Whitton
2020-07-04 5:34 ` Add -other-{window, frame} " Stephen Leake
2020-07-04 23:24 ` Sean Whitton
2020-07-06 0:58 ` Stephen Leake
2020-07-06 0:23 ` Juri Linkov
2020-07-06 3:31 ` Stefan Monnier
2020-07-06 22:57 ` Juri Linkov
2020-07-06 23:27 ` Drew Adams
2020-07-06 23:35 ` Stefan Monnier
2020-07-07 23:52 ` Juri Linkov
2020-07-08 4:06 ` Stefan Monnier
2020-07-09 0:24 ` Juri Linkov [this message]
2020-07-09 23:58 ` 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
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=87r1tl358h.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen_leake@stephe-leake.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 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).