all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: managing windows in two frames
Date: Wed, 04 Sep 2013 16:22:13 -0500	[thread overview]
Message-ID: <85ppso1dve.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwvd2oocrus.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 04 Sep 2013 15:33:58 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>>> `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.

Yes, that makes sense.

>>> 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.

Ok; that makes sense as a user interface.

Do you have a hint about how to implement it? I've never seen code tied
to a prefix, but I'm happy to experiment.

> Of course, other such prefixes could be used, such as C-x 4.  

Right, that would be "other window" (C-x 4 f is
`find-file-other-window'), while C-x 5 is "other frame". 

> 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.

C-x 6 is available. But display-buffer is not used for displaying a
buffer in the current window now, so I think this cannot be handled by
the same mechanism. At least not without major changes.

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

Right. Designing a UI to let users select a particular window is a
challenge. I may think about that later ...

-- 
-- Stephe



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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85ppso1dve.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.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.