From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>,
Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: RE: managing windows in two frames
Date: Wed, 4 Sep 2013 14:33:32 -0700 (PDT) [thread overview]
Message-ID: <b9e2ba25-0658-483d-aa29-c17c0c23d718@default> (raw)
In-Reply-To: <jwvd2oocrus.fsf-monnier+emacs@gnu.org>
> Make C-x 5 a prefix key which sets display-buffer-overriding-action for
> the duration of the next command.
>
> So C-x 5 C-x C-f will do the same as what you currently get with C-x 5 f
> (of course, we'd also preserve a C-x 5 f binding for backward
> compatibility,
For more than just that, no? `C-x 5 C-x C-f' is not as simple as
`C-x 5 f'. Occam would grumble.
Yes, Occam might be somewhat happy to eliminate the "extra" commands
`*-other-window' and `*-other-frame', and just have `*'. But the devil
is in the details. It's not clear, so far, whether users would find
this simpler or more complicated.
> and we wouldn't need find-file-other-frame any more,
Do you mean only for `C-x 5 f'? Someone will likely want to bind such
a command (or whatever it becomes) to additional keys, no? Sure s?he
could make do with a lambda expression or whatever, if necessary.
But why? (It's not clear to me just what you have in mind.)
> although we'd also have to keep it for backward compatibility).
For more than just that, I expect...
> Of course, other such prefixes could be used, such as C-x 4.
BTW, what do you do with `C-x 4 C-x 5 C-x C-f'? By your description,
I guess that does the same thing as `C-x 4 f'?
> And as Martin mentions, we'd want one that can say "display in current
> window". That should be no harder to define than C-x 4 or C-x 5.
Suppose it were `C-x 6', for kicks. Would `C-x 6 C-x 4 C-x 5 C-x C-f'
then be the same as `C-x C-f'?
Will you at least be keeping `C-x C-f' "for backward compatibility"?
> More generally you could define such a prefix key that lets you specify
> a particular window to use in the next command.
Could we see a spec of some kind (better description), before the
implementation and possible deprecations?
next prev parent reply other threads:[~2013-09-04 21:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 9:11 managing windows in two frames Stephen Leake
2013-09-03 12:52 ` martin rudalics
2013-09-04 18:16 ` Stephen Leake
2013-09-04 18:24 ` Stephen Leake
2013-09-04 19:33 ` Stefan Monnier
2013-09-04 21:22 ` Stephen Leake
2013-09-06 10:53 ` martin rudalics
2013-09-07 8:49 ` Stephen Leake
2013-09-07 9:37 ` martin rudalics
2013-09-07 13:19 ` Stephen Leake
2013-09-08 7:56 ` martin rudalics
2013-09-04 21:33 ` Drew Adams [this message]
2013-09-06 10:52 ` martin rudalics
2013-09-06 13:22 ` Stefan Monnier
2013-09-06 10:52 ` martin rudalics
2013-09-07 8:56 ` Stephen Leake
2013-09-07 9:37 ` martin rudalics
2013-09-07 13:29 ` Stephen Leake
2013-09-03 13:59 ` Stefan Monnier
2013-09-03 14:15 ` martin rudalics
2013-09-03 14:30 ` Stefan Monnier
2013-09-03 16:23 ` martin rudalics
2013-09-03 20:34 ` Stefan Monnier
2013-09-04 6:25 ` martin rudalics
2013-09-04 13:24 ` Stefan Monnier
2013-09-04 15:04 ` martin rudalics
2013-09-04 17:44 ` Stefan Monnier
2013-09-06 10:53 ` martin rudalics
2013-09-06 13:44 ` Stefan Monnier
2013-09-06 17:14 ` martin rudalics
2013-09-06 19:00 ` Stefan Monnier
2013-09-07 9:37 ` martin rudalics
2013-09-08 17:55 ` Stefan Monnier
2013-09-09 8:10 ` martin rudalics
2013-09-09 14:05 ` Stefan Monnier
2013-09-04 18:19 ` Stephen Leake
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=b9e2ba25-0658-483d-aa29-c17c0c23d718@default \
--to=drew.adams@oracle.com \
--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 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.