[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: switch-to-buffer-other-frame fails to pop-up window

From: Mark T. Kennedy
Subject: Re: switch-to-buffer-other-frame fails to pop-up window
Date: Wed, 05 Dec 2007 14:55:43 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20071031 Thunderbird/ Mnenhy/

two observations:

1) contrast the behavior of 'c-x 5 b' with 'c-x 4 b'.  'c-x 4 b' always forces 
the creation of two
different windows, even when displaying the same buffer.  'c-x 5 b' does not 
always force the
creation of two frames.

2) one might guess that 'switch-to-buffer-other-frame' is essentially a wrapper 
sets 'pop-up-frames' to 't' and then calls display-buffer (and it is).
while the behavior of display-buffer is meticulously documented, the observed
behavior clashes with the documentation for 'pop-up-frames'.  now if it were
called "maybe-pop-up-frames" or "frequently-pop-up-frames", i wouldn't feel
so bad, but... :-).

so i'm requesting (not demanding :-) a change in behavior.

what use case would clash with a change like this?


martin rudalics wrote:
>  > 1) start emacs with "-Q"
>  > 2) type "c-x b foo", then "c-x 2", and then "c-x b".
>  >    now "*scratch* and "foo" are displayed in two windows
>  >    on the original single frame.
> At this moment the window displaying "foo" is _not_ selected.
>  > 3) now type "c-x 5 b foo" and see that a new frame is not
>  >    popped up.
> But the window displaying "foo" should be selected now.  This is the
> expected behavior of `display-buffer' which is mentioned in the
> doc-string of `switch-to-buffer-other-frame'.
> Maybe `switch-to-buffer-other-frame' should _always_ display the buffer
> in another frame - that is call `display-buffer-other-frame' and select
> that frame (C-x 5 C-o doesn't _select_ the other frame).
>  > contrast this with "emacs -Q" and "c-x 4 b foo" followed by
>  > "c-x 5 b foo".
> Because at the time you invoke C-x 5 b foo here a window showing "foo"
> is selected.  Again this is the documented behavior of `display-buffer'.
> Just some explanations - feel free to demand a more intuitive behavior
> and/or description.  To me it's not entirely clear how to reconcile all
> possible use cases.

This communication and any attachments may contain confidential/proprietary 
information and is intended for information purposes only. It is not an 
invitation or offer to purchase interests from Diamondback.  Any representation 
to the contrary is unintentional.  This communication is intended only for the 
person(s) to whom it is addressed.  If you are not the intended recipient you 
are hereby notified that you have received this document in error and that any 
review, dissemination, distribution, or copying of this message or any 
attachments is not permitted.  If you have received this in error, please 
notify the sender immediately by e-mail and delete this message.  All e-mails 
sent to or received from this address will be received by Diamondback's company 
e-mail system and is subject to archival and possible review by someone other 
than the recipient.  This notice is automatically appended to each e-mail 
message leaving Diamondback.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]