all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
Cc: 8936@debbugs.gnu.org
Subject: bug#8936: 24.0.50; Incompatible change in the meaning of "other window"
Date: Sun, 26 Jun 2011 11:29:14 +0200	[thread overview]
Message-ID: <4E06FBEA.6010202@gmx.at> (raw)
In-Reply-To: <19974.24793.979873.787090@rgr.rgrjr.com>

 >    The problem is that C-x 4 b now creates a new frame to display the
 > buffer, instead of creating or reusing a window in the current frame.
 > This can be reproduced by typing "C-x 4 b" as the first thing in a fresh
 > "emacs -Q"; you will see the *Messages* buffer opened in a new frame.
 >
 >    This is in emacs trunk via git last updated today at 21:59:08 UTC.

Here a new window pops up.  Could you please step through the functions
`display-buffer-pop-up-window', `display-buffer-split-window' and
`display-buffer-split-window-1' to find out why splitting a window fails
on your system?

If Emacs can't split a window I currently make a new frame because the
doc-string of `switch-to-buffer-other-window' explicitly says that "The
selected window will be used only if there is no other choice" and
making a new frame _is_ another choice.  If people think that reusing
the selected window is a better choice I can easily do that.

Thanks, martin





  reply	other threads:[~2011-06-26  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-25 22:27 bug#8936: 24.0.50; Incompatible change in the meaning of "other window" Bob Rogers
2011-06-26  9:29 ` martin rudalics [this message]
2011-06-26 10:54   ` Eli Zaretskii
2011-06-26 12:12     ` martin rudalics
2011-06-26 12:42       ` Eli Zaretskii
2011-06-26 12:47         ` martin rudalics
2011-07-06  0:33   ` Bob Rogers

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=4E06FBEA.6010202@gmx.at \
    --to=rudalics@gmx.at \
    --cc=8936@debbugs.gnu.org \
    --cc=rogers-emacs@rgrjr.dyndns.org \
    /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.