GNU bug report logs -
#7368
display-buffer may not respect pop-up-frames value
Previous Next
Full log
View this message in rfc822 format
I've checked out window-pub and played with it bit. Basically,
everything worked great for me so far (note: I use default window
options). Didn't notice any regressions. The problem with
*Completions* is gone because in window-pub *Completions* is not
dedicated :-) Also, I liked that many functions moved from C to Lisp
(one can explore and tweak them much easier).
As a temporary solution to the bug I now use the following code. It
has some minor issues (i.e. if *Completions* is above code buffer, and
I switch to interpreter, code buffer would come above and interpreter
buffer would come below), but I can definitely live with it. However,
proper upstream fix would still be very welcome.
(defun my-display-buffer (buffer flag)
(when (not (eq (buffer-name buffer) "*Completions*"))
(let ((completions-window (get-buffer-window "*Completions*")))
(when completions-window
(quit-window nil completions-window))))
(let (display-buffer-function)
(display-buffer buffer flag)))
(setq display-buffer-function 'my-display-buffer)
Thanks for your support,
Andrey Paramonov
This bug report was last modified 10 years and 237 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.