From: Juanma Barranquero <lekktu@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: martin rudalics <rudalics@gmx.at>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: switch-to-buffer: for interactive use only
Date: Fri, 8 Jul 2011 22:34:04 +0200 [thread overview]
Message-ID: <CAAeL0SRuKuo--yzpqV+TUqr_qsjeiSuuFuTLVnwQxr8_bpTeww@mail.gmail.com> (raw)
In-Reply-To: <87d3hkmt0k.fsf@stupidchicken.com>
On Fri, Jul 8, 2011 at 22:12, Chong Yidong <cyd@stupidchicken.com> wrote:
> Why does `switch-to-buffer' need to only affect the selected window?
> What's wrong with using a different window, instead of signaling a
> error, if the selected window can't be used?
That would resurrect the bug recently fixed in bs-cycle-next where it
opened another window when the selected one was strongly dedicated. It
is called "cycle", not "bring-me": either it can cycle a new buffer
into the window, or it should say that it cannot. That's what it does
now, and that's the right thing to do.
For some operations on a buffer with a strongly dedicated window, it
makes sense to pop up another window; for some others, it does not.
Conflating both is never going to be a good answer. Well, strictly
speaking, we can do that and use `display-buffer-alist' to allow the
user to override it; but bs-cycle-next, and operations of that kind,
should do the right thing out of the box.
Juanma
next prev parent reply other threads:[~2011-07-08 20:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 21:40 switch-to-buffer: for interactive use only Glenn Morris
2011-07-05 23:23 ` Juanma Barranquero
2011-07-05 23:32 ` Glenn Morris
2011-07-05 23:34 ` Juanma Barranquero
2011-07-05 23:41 ` Juanma Barranquero
2011-07-06 1:18 ` Stefan Monnier
2011-07-06 1:49 ` Glenn Morris
2011-07-06 2:27 ` Glenn Morris
2011-07-06 5:55 ` Andreas Röhler
2011-07-06 21:10 ` Chong Yidong
2011-07-07 9:19 ` Štěpán Němec
2011-07-07 19:52 ` Stefan Monnier
2011-07-07 20:50 ` Chong Yidong
2011-07-07 21:11 ` Stefan Monnier
2011-07-07 23:39 ` Chong Yidong
2011-07-08 0:09 ` Juanma Barranquero
2011-07-08 1:12 ` Chong Yidong
2011-07-08 6:44 ` martin rudalics
2011-07-08 6:44 ` martin rudalics
2011-07-08 6:43 ` martin rudalics
2011-07-08 12:57 ` Stefan Monnier
2011-07-08 14:03 ` martin rudalics
2011-07-08 15:46 ` Stefan Monnier
2011-07-08 16:45 ` martin rudalics
2011-07-08 18:46 ` Stefan Monnier
2011-07-08 20:12 ` Chong Yidong
2011-07-08 20:34 ` Juanma Barranquero [this message]
2011-07-08 20:50 ` Chong Yidong
2011-07-08 23:16 ` Juanma Barranquero
2011-07-09 2:35 ` Chong Yidong
2011-07-09 3:09 ` Stefan Monnier
2011-07-09 8:45 ` martin rudalics
2011-07-11 3:41 ` Stefan Monnier
2011-07-11 9:43 ` martin rudalics
2011-07-09 19:25 ` Chong Yidong
2011-07-10 9:00 ` martin rudalics
2011-07-10 13:09 ` Chong Yidong
2011-07-10 13:31 ` martin rudalics
2011-07-11 3:45 ` Stefan Monnier
2011-07-11 14:56 ` Chong Yidong
2011-07-12 4:25 ` Stefan Monnier
2011-07-12 8:36 ` martin rudalics
2011-07-13 15:42 ` Chong Yidong
2011-07-13 17:18 ` martin rudalics
2011-07-13 21:53 ` Chong Yidong
2011-07-09 8:45 ` martin rudalics
-- strict thread matches above, loose matches on Subject: below --
2011-07-13 22:13 grischka
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=CAAeL0SRuKuo--yzpqV+TUqr_qsjeiSuuFuTLVnwQxr8_bpTeww@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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.