From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "help-gnu-emacs@gnu.org List" <help-gnu-emacs@gnu.org>,
"João Távora" <joaotavora@gmail.com>,
emacs-devel@gnu.org
Subject: Re: frames dedicated to buffers, or, always see specific buffers in a specific frame
Date: Sat, 13 Apr 2013 10:01:50 +0200 [thread overview]
Message-ID: <516910EE.2070109@gmx.at> (raw)
In-Reply-To: <jwvk3o7k8ol.fsf-monnier+emacs@gnu.org>
> I don't see why that would be necessary: switch-to-buffer-other-window
> calls display-buffer (well, pop-to-buffer) so it should honor
> display-buffer-alist.
Correct, obviously.
> Other than switch-to-buffer they all go through display-buffer and obey
> the display-buffer-* hooks.
>
> switch-to-buffer is special because there are various circumstances
> where it's more important for it to only affect the selected-window then
> it is to display the specified buffer.
Ideally, `switch-to-buffer' does not get called from Lisp code.
Unfortunately, there are too many instances of such calls to change them
all.
martin
next prev parent reply other threads:[~2013-04-13 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 9:28 frames dedicated to buffers, or, always see specific buffers in a specific frame martin rudalics
2013-04-12 12:12 ` João Távora
2013-04-12 13:13 ` João Távora
2013-04-12 14:15 ` martin rudalics
[not found] ` <CALDnm50Q=eNA6rgUS-DQD2RLuE=kyizGpYWyENVU=2Py+-MTig@mail.gmail.com>
2013-04-14 18:42 ` João Távora
2013-04-15 7:11 ` martin rudalics
2013-04-12 16:45 ` Stefan Monnier
2013-04-13 8:01 ` martin rudalics [this message]
2013-04-14 18:18 ` João Távora
-- strict thread matches above, loose matches on Subject: below --
2013-04-10 20:52 João Távora
2013-04-10 21:30 ` Steven Degutis
2013-04-11 1:22 ` João Távora
2013-04-11 12:42 ` Stefan Monnier
2013-04-11 12:46 ` Stefan Monnier
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=516910EE.2070109@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=joaotavora@gmail.com \
--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 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.