GNU bug report logs - #8865
24.0.50; `display-buffer' does not respect `pop-up-frames'

Previous Next

Full log

Message #20 received at 8865 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 'Juri Linkov' <juri <at> jurta.org>, 8865 <at> debbugs.gnu.org,
	'Stefan Monnier' <monnier <at> iro.umontreal.ca>
Subject: Re: bug#8865: 24.0.50;
	`display-buffer' does not respect `pop-up-frames'
Date: Wed, 15 Jun 2011 18:26:06 +0200

> 2. Anyway, I tried your proposed redefinition of
> `display-buffer-normalize-specifiers-1', just in case, and it does not have any
> effect on this bug.  See below: the `other-window' value is not something
> special in my code, and the fix is certainly not to treat that particular symbol
> as a special case.

With the redefinition of `display-buffer-normalize-specifiers-1' doing

(let ((pop-up-frames t))
  (display-buffer (get-buffer-create "*foo*") 'other-window))

pops up a new frame.  So do

(let ((pop-up-frames t))
  (display-buffer (get-buffer-create "*foo*") 4))

and

(let ((pop-up-frames t))
  (display-buffer (get-buffer-create "*foo*") "Drew"))

Evaluating

(setq pop-up-frames t)

and subsequently doing C-x 4 b pops up the buffer in a new frame.  What
do you get?  What more do you want?

martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.