unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: managing windows in two frames
Date: Wed, 04 Sep 2013 15:33:58 -0400	[thread overview]
Message-ID: <jwvd2oocrus.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <858uzcbggs.fsf@stephe-leake.org> (Stephen Leake's message of "Wed, 04 Sep 2013 13:16:03 -0500")

>> `display-buffer' decisions are currently not based on a prefix argument
>> given.
> Right; that's new. I find it very convenient.

But it's fundamentally broken (the prefix arg is an argument to the
command being run, and the relationship between the command being run
and the call to `display-buffer' can be arbitrary).
IOW it's perfectly fine for personal use but we can't use that in
lisp/window.el.

>> Maybe we can reconcile your idea with Stefan's proposal to use
>> special prefixes for `display-buffer'-based functions.
> Searching the emacs-devel archives, I found:
> http://lists.gnu.org/archive/html/emacs-devel/2011-09/msg00299.html
> http://lists.gnu.org/archive/html/emacs-devel/2011-08/msg00481.html
> That doesn't give a very concrete proposal; can provide a better link?

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, and we wouldn't need find-file-other-frame any more,
although we'd also have to keep it for backward compatibility).

Of course, other such prefixes could be used, such as C-x 4.  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.

More generally you could define such a prefix key that lets you specify
a particular window to use in the next command.


        Stefan



  parent reply	other threads:[~2013-09-04 19: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 [this message]
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
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

  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=jwvd2oocrus.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --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).