From: Chong Yidong <cyd@stupidchicken.com>
To: Juanma Barranquero <lekktu@gmail.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, 08 Jul 2011 22:35:32 -0400 [thread overview]
Message-ID: <87zkkokwp7.fsf@stupidchicken.com> (raw)
In-Reply-To: <CAAeL0SRwaC1XkktK5_5+bOMZ9yYCG2FE-gOhTtrKv3Y_5qJkhQ@mail.gmail.com> (Juanma Barranquero's message of "Sat, 9 Jul 2011 01:16:42 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
>> So, if creating a new window is the wrong thing for bs-cycle-next, it
>> should be bs-cycle-next that changes---e.g. by changing from
>> switch-to-buffer to set-window-buffer---not everything else in Emacs.
>
> I don't remember saying that it is the rest of Emacs which must be
> changed; only that there are two different use cases, and we must
> cater to both.
Fair enough. So, I propose the following:
- Make switch-to-buffer basically do
(pop-to-buffer buffer-or-name 'same-window norecord label)
- Make pop-to-buffer-same-window an alias for switch-to-buffer.
(This means to add an optional LABEL arg to switch-to-buffer, for
consistency with pop-to-buffer-same-window.)
- Remove the "interactive use only" flag from switch-to-buffer.
- For those places that intend the "act on the selected window"
behavior---which is the minority---change the code to call
(set-window-buffer (selected-window) buffer), instead of
switch-to-buffer.
How's that?
next prev parent reply other threads:[~2011-07-09 2:35 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
2011-07-08 20:50 ` Chong Yidong
2011-07-08 23:16 ` Juanma Barranquero
2011-07-09 2:35 ` Chong Yidong [this message]
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=87zkkokwp7.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--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.