GNU bug report logs - #7368
display-buffer may not respect pop-up-frames value

Previous Next

Full log

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

From: Андрей Парамонов
	<cmr.pent <at> gmail.com>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 7368 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#7368: display-buffer a softly dedicated window
Date: Thu, 18 Nov 2010 13:36:59 +0300

2010/11/18 martin rudalics <rudalics <at> gmx.at>:
>> comint.el forces *Completions* to close and shows the interpreter
>> immediately, in its place. That's what I want, exactly. Showing the
>> interpreter in place of *Completions* would have the same effect, so
>> it's what I want, too.
>
> I've looked into comint.el.  It's apparently based on window
> configurations and restores the old configuration when you do
> `choose-completion' or type SPACE.  I don't see where it deletes the
> window when you do something else.  Very contrived code.

If you are interested you may check the example I provided in my
recent emacs.devel thread. *Completions* is somehow closed before
comint-dynamic-list-completions is finished
(comint-dynamic-list-completions doesn't exit immediately upon showing
*Completions*).

> Hm...  What about setting `display-buffer-function' to something like:
>
> (defun my-display-buffer (buffer flag)
>  (let (window display-buffer-function)
>    (when (and (= (length (window-list)) 2)
>               (setq window (get-buffer-window "*Completions*")))
>      (set-window-dedicated-p window nil))
>    (display-buffer buffer flag)))
>

Hm, nice idea. But isn't display-buffer-function called from
display-buffer (infinite recursion)? I'll check it when I get to my
Emacs box.

Best wishes,
Andrey Paramonov

Previous Next

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