* pop-to-buffer-same-window
@ 2011-09-01 16:14 Chong Yidong
2011-09-01 16:25 ` pop-to-buffer-same-window Chong Yidong
2011-09-02 2:43 ` pop-to-buffer-same-window Stefan Monnier
0 siblings, 2 replies; 5+ messages in thread
From: Chong Yidong @ 2011-09-01 16:14 UTC (permalink / raw)
To: emacs-devel
Was there any particular reason for adding a separate
pop-to-buffer-same-window function, as opposed to adding an additional
meaning to pop-to-buffer's OTHER-WINDOW argument, i.e.
(pop-to-buffer buffer 'same-window)
? I don't recall any such discussion when pop-to-buffer-same-window was
originally introduced, but could be mistaken.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: pop-to-buffer-same-window
2011-09-01 16:14 pop-to-buffer-same-window Chong Yidong
@ 2011-09-01 16:25 ` Chong Yidong
2011-09-02 2:43 ` pop-to-buffer-same-window Stefan Monnier
1 sibling, 0 replies; 5+ messages in thread
From: Chong Yidong @ 2011-09-01 16:25 UTC (permalink / raw)
To: emacs-devel
Chong Yidong <cyd@stupidchicken.com> writes:
> Was there any particular reason for adding a separate
> pop-to-buffer-same-window function, as opposed to adding an additional
> meaning to pop-to-buffer's OTHER-WINDOW argument, i.e.
>
> (pop-to-buffer buffer 'same-window)
>
> ? I don't recall any such discussion when pop-to-buffer-same-window was
> originally introduced, but could be mistaken.
I guess the main reason for a separate `pop-to-buffer-same-window' is to
provide a separate command for users to bind to. Is that the reason?
If so, is `pop-to-buffer-same-window' supposed to supplant interactive
calls to switch-to-buffer?
Someone who uses dedicated windows (Stefan?) should probably weigh in.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: pop-to-buffer-same-window
2011-09-01 16:14 pop-to-buffer-same-window Chong Yidong
2011-09-01 16:25 ` pop-to-buffer-same-window Chong Yidong
@ 2011-09-02 2:43 ` Stefan Monnier
2011-09-02 14:26 ` pop-to-buffer-same-window Chong Yidong
1 sibling, 1 reply; 5+ messages in thread
From: Stefan Monnier @ 2011-09-02 2:43 UTC (permalink / raw)
To: Chong Yidong; +Cc: emacs-devel
> Was there any particular reason for adding a separate
> pop-to-buffer-same-window function, as opposed to adding an additional
> meaning to pop-to-buffer's OTHER-WINDOW argument, i.e.
> (pop-to-buffer buffer 'same-window)
I think the reason was so as to avoid adding some special handling for
a new special value `same-window'. This second argument should be
a RULE (previously known as ACTION) and the special-case of
`not-this-window' is annoying enough.
This said, with the new switch-to-buffer's FORCE-SAME-WINDOW, we don't
need pop-to-buffer-same-window since switch-to-buffer works just as well.
Stefan
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-09-02 14:50 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-01 16:14 pop-to-buffer-same-window Chong Yidong
2011-09-01 16:25 ` pop-to-buffer-same-window Chong Yidong
2011-09-02 2:43 ` pop-to-buffer-same-window Stefan Monnier
2011-09-02 14:26 ` pop-to-buffer-same-window Chong Yidong
2011-09-02 14:50 ` pop-to-buffer-same-window Stefan Monnier
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).