From: Sean Whitton <spwhitton@spwhitton.name>
To: Juri Linkov <juri@linkov.net>, emacs-devel@gnu.org
Subject: Add -other-{window,frame} variants of project-prefix-map commands
Date: Fri, 03 Jul 2020 17:54:00 -0700 [thread overview]
Message-ID: <87blkw5cd3.fsf@iris.silentflame.com> (raw)
Hello,
It seems like it would be a good idea to have
C-x 4 p f
be like
C-x 4 4 C-x p f
C-x 5 p e
be like
C-x 5 5 C-x p e
etc., since many of the commands in project-prefix-map involve switching
to another buffer. Certainly project-switch-project, project-find-file
and project-switch-to-buffer would be wanted.
Rather than add definitions of project-find-file-other-window,
project-eshell-other-frame etc., maybe
`display-buffer-override-next-command' could be used so that pressing
C-x 4 p really is just like pressing C-x 4 4 C-x p.
The only disadvantage I can see is that commands like C-x 4 p k would
also be bound and those don't really make sense.
What would be the cleanest way to try to do this?
Thanks.
--
Sean Whitton
next reply other threads:[~2020-07-04 0:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 0:54 Sean Whitton [this message]
2020-07-04 5:34 ` Add -other-{window, frame} variants of project-prefix-map commands 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
2020-07-09 23:58 ` Juri Linkov
2020-07-05 6:13 ` bug#42210: Add -other-window " Sean Whitton
2020-07-05 14:41 ` Eli Zaretskii
2020-07-05 18:35 ` Drew Adams
2020-07-05 20:25 ` Sean Whitton
2020-07-06 0:00 ` Drew Adams
2020-07-06 0:19 ` Juri Linkov
2020-07-06 1:58 ` Sean Whitton
2020-07-06 22:59 ` Juri Linkov
2020-07-08 6:27 ` Sean Whitton
2020-07-09 0:10 ` Juri Linkov
2020-07-11 17:09 ` Sean Whitton
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=87blkw5cd3.fsf@iris.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=emacs-devel@gnu.org \
--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.