From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Arthur Miller <arthur.miller@live.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Universal/prefix argument for "other window" redirection?
Date: Thu, 08 Apr 2021 21:18:25 -0700 [thread overview]
Message-ID: <87pmz4jdke.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <AM9PR09MB497756A9CE1003477E0632F296749@AM9PR09MB4977.eurprd09.prod.outlook.com> (Arthur Miller's message of "Thu, 08 Apr 2021 18:11:23 +0200")
Arthur Miller <arthur.miller@live.com> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> What I would like is to have all the cursor motion stuff, expression
>>> evals etc, work on in other window so I don't need to switch back and
>>> forth two buffers (I like to work with two buffers side-by-side). I
>>> wonder if there is already something I could use; prefix
>>> command/universal prefix whatever, to autmoatically modify behaviour of
>>> interactive commands involved or do I have to write my own (if it's
>>> possible :))?
>>
>> OT1H you mention universal-prefix (which only affects the very next
>> command) but OTOH you say "all the cursor motion stuff ...".
>>
>> For the "all the cursor ..." case, it seems you're saying all the
>> commands should operate on the other window, which is exactly what you
>> get after `C-x o`, so your description needs more details to know what
>> you really mean.
>
> Haha, yes, I think I myself need more details to know what I mean :).
>
> I don't know myself what I really want. I find myself switching a lot
> between two windows, which sometimes feels redundant. Maybe it is just
> the shortcut, C-x o, or in my case C-v o. After playing with Gregory's
> example, I am thinking of just binding the other-window to the `§` key.
> Maybe that itself will be enough for somewhat "smoother" experience.
I wrote a command that sends the cursor to another buffer window, and
lets you do whatever you want in that window, until you hit "q" (this is
a special-mode buffer so insertion isn't an issue), whereupon it pops
you back to the original window. It uses a transient keymap to do that,
which is yet another approach you could consider.
https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/ebdb-mua.el?h=externals/ebdb#n1244
next prev parent reply other threads:[~2021-04-09 4:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 9:37 Universal/prefix argument for "other window" redirection? Arthur Miller
2021-04-08 12:16 ` Gregory Heytings
2021-04-08 15:58 ` Arthur Miller
2021-04-08 14:56 ` Stefan Monnier
2021-04-08 16:11 ` Arthur Miller
2021-04-08 17:01 ` Yuri Khan
2021-04-08 17:42 ` Arthur Miller
2021-04-08 17:57 ` Stefan Monnier
2021-04-08 18:26 ` Arthur Miller
2021-04-09 4:18 ` Eric Abrahamsen [this message]
2021-04-09 7:58 ` Arthur Miller
2021-04-08 22:59 ` Arthur Miller
2021-04-08 23:03 ` Stefan Monnier
2021-04-08 19:04 ` Sean Whitton
2021-04-08 21:14 ` Arthur Miller
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=87pmz4jdke.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).