all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 8865@debbugs.gnu.org
Subject: bug#8865: 24.0.50; `display-buffer' does not respect `pop-up-frames'
Date: Tue, 14 Jun 2011 21:08:43 +0200	[thread overview]
Message-ID: <4DF7B1BB.6050704@gmx.at> (raw)
In-Reply-To: <BE1586A46B7B45DC91E7534026397219@us.oracle.com>

 > I have non-nil `pop-up-frames'.  I use the following function via `M-x
 > find-library-other-window frame.el'.  It should find the library in a
 > separate frame.  Instead, it finds it in another window of the current
 > frame - i.e., it splits the current window and puts it in one of those
 > two windows.

Emacs has a lot of commands postfixed with -other-window and
-other-frame.  For example, `find-file-other-window' or
`switch-to-buffer-other-window' traditionally find a file or switch to a
buffer in another window on the same frame.  By this convention,
`find-library-other-window' is not supposed to pop up a new frame.

If we want to maintain compatibility with the old behavior in this and
similar cases we'd have to segregate a set of reserved values for the
second argument of `display-buffer'.  Preserving the classic "non-nil"
behavior is impossible if we want to use the new `display-buffer' code
(originally I favored let-binding to achieve that behavior but using an
argument was proposed by Stefan Monnier and overloading the second
argument by Juri Linkov - at the time that was discussed there were no
objections).

I have no objections interpreting the argument value `t' in the sense
that when `pop-up-frames' is non-nil and not unset, `display-buffer'
tries to pop up a new frame before it tries to pop up a new window.

martin





  reply	other threads:[~2011-06-14 19:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 18:14 bug#8865: 24.0.50; `display-buffer' does not respect `pop-up-frames' Drew Adams
2011-06-14 19:08 ` martin rudalics [this message]
2011-06-14 19:43   ` Drew Adams
2011-06-15  9:24     ` martin rudalics
2011-06-15 16:14       ` Drew Adams
2011-06-15 16:26         ` martin rudalics
2011-06-15 17:11           ` Drew Adams
2011-06-15 17:44             ` martin rudalics
2011-06-15 17:53               ` Drew Adams
2011-06-15 22:15                 ` Drew Adams
2011-06-16 13:01                   ` martin rudalics
2011-06-16 14:01                     ` Drew Adams
2011-06-16 15:08                       ` martin rudalics
2011-06-16 16:03                         ` Drew Adams
2011-06-17 15:46                           ` martin rudalics
2011-06-17 18:31                             ` Drew Adams
2011-06-19 17:43                               ` Drew Adams
2011-06-19 18:50                                 ` martin rudalics
2011-06-19 20:13                                 ` Drew Adams
2011-06-16 13:09                   ` Stefan Monnier
2011-06-16 14:02                     ` Drew Adams
2011-06-17  2:44                       ` Stefan Monnier
2011-06-17 15:08                         ` Drew Adams
2011-06-17 16:21                           ` Stefan Monnier
2011-06-17 18:31                             ` Drew Adams
2011-06-17 21:46                               ` Stefan Monnier
2011-06-17 23:55                                 ` Drew Adams
2011-06-18  1:51                                   ` Stefan Monnier
2011-06-16  8:45               ` martin rudalics

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=4DF7B1BB.6050704@gmx.at \
    --to=rudalics@gmx.at \
    --cc=8865@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.