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

[martin rudalics <rudalics@gmx.at>]

 > 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