From: martin rudalics <rudalics@gmx.at>
To: joaotavora@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: frames dedicated to buffers, or, always see specific buffers in a specific frame
Date: Fri, 12 Apr 2013 11:28:23 +0200 [thread overview]
Message-ID: <5167D3B7.2080408@gmx.at> (raw)
> (defadvice switch-to-buffer (around joaot/browse-buffer-maybe activate)
> (if (joaot/browse-buffer-p buffer-or-name nil)
> (display-buffer buffer-or-name)
> ad-do-it))
>
> Does anyone know of a less hackish way to do this? The defadvice is
> particularly nasty... Do you see this breaking anything important that
> I'm not seeing??
`switch-to-buffer' uses `pop-to-buffer' to make sure the window
displaying the buffer is selected. You use `display-buffer' which
doesn't necessarily make the window selected - IIUC you rely on the
window manager to select the window.
Other from that I don't see anything hackish with your approach if the
idea is to make `switch-to-buffer' do what you want when it's called
from other code (which ideally should not happen). In this case you
might also want to advice `switch-to-buffer-other-window' accordingly.
Interactively, you obviously should define your own function and bind it
to C-x b.
martin
next reply other threads:[~2013-04-12 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 9:28 martin rudalics [this message]
2013-04-12 12:12 ` frames dedicated to buffers, or, always see specific buffers in a specific frame 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
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=5167D3B7.2080408@gmx.at \
--to=rudalics@gmx.at \
--cc=help-gnu-emacs@gnu.org \
--cc=joaotavora@gmail.com \
/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.