|
From: | Stefan Monnier |
Subject: | Re: display-buffer-other-frame - useful? doc string? |
Date: | Sat, 05 Apr 2008 22:28:27 -0400 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
> I thought this had been fixed. CVS shows that the code and doc string > are still problematic. The only thing that was done was to comment out > the silly `lower-frame' and `make-frame(-in)-visible' dance and add > a comment saying that that was harmful and silly. (That at least > stopped the frame from being lowered.) The problem is that display-buffer doesn't work as it should. So we should fix display-buffer. Can you try the following: (lexical-let ((f pop-up-frame-function)) (setq pop-up-frame-function (lambda () (let ((win (selected-window))) (unwind-protect (funcall f) (when (window-live-p win) (select-window win) (select-frame-set-input-focus (window-frame win)))))))) If this works, can you try to inline select-frame-set-input-focus and remove each part one by one until you figure out which part is necessary and which part isn't. The difficulty is that select-frame-set-input-focus doesn't do the right thing in my situation: it raises the current frame whereas it shouldn't be doing that. Stefan
[Prev in Thread] | Current Thread | [Next in Thread] |