From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: managing windows in two frames
Date: Sat, 07 Sep 2013 03:49:35 -0500 [thread overview]
Message-ID: <85hadx584g.fsf@stephe-leake.org> (raw)
In-Reply-To: <5229B417.60006@gmx.at> (martin rudalics's message of "Fri, 06 Sep 2013 12:53:11 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> 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.
>
> `display-buffer-same-window'? Or what am I missing?
`find-file' does not call `display-buffer'; `find-file-other-window'
does call `display-buffer'. (I just checked by enabling Edebug in
display-buffer.)
`find-file' calls `switch-to-buffer' which calls `pop-to-buffer'.
The same is true for all the other "put a buffer in this window"
user level functions I've encountered.
`display-buffer-same-window' is an action for `display-buffer'.
Ah! We could change the implementation of `find-file' to use
`display-buffer' with an action of `display-buffer-same-window'; that
action would be changed by prefix C-x 4 or C-x 5.
`find-file-other-window' could then be implemented by setting
`display-buffer-overriding-action' and calling `find-file'.
That would make sense, and should be mostly transparent to users. All
the other similar functions would have to be changed in a similar way -
I haven't tried to enumerate them. We could implement C-x 4 and 5 for
the current uses of `display-buffer' first, and see how people like it.
--
-- Stephe
next prev parent reply other threads:[~2013-09-07 8:49 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 [this message]
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=85hadx584g.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.