From: martin rudalics <rudalics@gmx.at>
To: "João Távora" <joaotavora@gmail.com>
Cc: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: frames dedicated to buffers, or, always see specific buffers in a specific frame
Date: Mon, 15 Apr 2013 09:11:23 +0200 [thread overview]
Message-ID: <516BA81B.3040904@gmx.at> (raw)
In-Reply-To: <CALDnm53SfPkTDaHyj+PGznC15Meth4=cf6NngYhP8K+sX-e5+Q@mail.gmail.com>
>> So for making this general purpose you should use `pop-to-buffer'
>> instead of `display-buffer'.
>
> Yes, that works too. Why exactly is this more general purpose?
I meant that if you really want to use this as a subtitute for
`switch-to-buffer' you should make sure the window and frame get
selected. They don't necessarily using `display-buffer' alone.
> Also, ido has these `ido-default-buffer-method' and
> `ido-default-file-method' that can be set to various options to
> control how buffer appears.
>
> But the way these options implemented does not bring them all to
> `display-buffer', which sometimes precludes user's control. Should't
> they be implemented via `display-buffer-alist', keeping any of the
> user's entries on top?
Doesn't setting `ido-default-buffer-method' to `display' work? Maybe we
could add `pop-to-buffer' to the default methods.
> Pity. But what about making `switch-to-buffer' delegate to
> `display-buffer' too? It could dinamically bind `display-buffer-alist'
> to display and select the buffer, but keeping any existing entries
> (probably set by the user, or other programs) on top.
>
> If that resulted in `switch-to-buffer' not switching to the buffer's
> window, it could not be considered unexpected behaviour, since
> ultimately the user set `display-buffer-alist' himself.
The basic idea of the `switch-to-buffer' functions is to bypass the
`display-buffer' customizations. That is, by default you display a
buffer in a certain manner but always can use `switch-to-buffer' to
override that default behavior.
martin
next prev parent reply other threads:[~2013-04-15 7:11 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 [this message]
2013-04-12 16:45 ` Stefan Monnier
2013-04-13 8:01 ` martin rudalics
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
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=516BA81B.3040904@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.
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).