all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mark T. Kennedy" <mkennedy@diamondbackcap.com>
To: martin rudalics <rudalics@gmx.at>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: switch-to-buffer-other-frame fails to pop-up window
Date: Wed, 05 Dec 2007 14:55:43 -0500	[thread overview]
Message-ID: <4757023F.6090602@diamondbackcap.com> (raw)
In-Reply-To: <475503CA.70502@gmx.at>


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 that
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?

/mark

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 a
 rchival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.





  reply	other threads:[~2007-12-05 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 14:48 switch-to-buffer-other-frame fails to pop-up window Mark T. Kennedy
2007-12-04  7:37 ` martin rudalics
2007-12-05 19:55   ` Mark T. Kennedy [this message]
2007-12-05 22:11     ` martin rudalics
2007-12-06 18:43       ` Mark T. Kennedy
2007-12-06 19:48         ` Drew Adams
2007-12-06 20:11           ` Mark T. Kennedy
2007-12-06 22:06             ` Drew Adams
2007-12-07 16:39               ` Mark T. Kennedy
2007-12-07 17:18                 ` Drew Adams
2007-12-07 19:41                 ` Mark T. Kennedy

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=4757023F.6090602@diamondbackcap.com \
    --to=mkennedy@diamondbackcap.com \
    --cc=bug-gnu-emacs@gnu.org \
    --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.