|Subject:||bug#14604: 18.104.22.168; Possibly incorrect behaviour of frame-selected-window|
|Date:||Wed, 30 Oct 2013 22:40:31 +0000|
Thanks!EvgeniOn Wed, Oct 30, 2013 at 5:50 PM, Stefan Monnier <address@hidden> wrote:
> (defvar user-selected-window nil)That will usually work, except for corner-cases where redisplay happens
> (defun register-user-location ()
> (setq user-selected-window (selected-window)))
> (add-hook 'post-command-hook 'register-user-location)
> '(:eval (if (eq user-selected-window (selected-window))
in the middle of a command, or when the selected window is modified
between commands (e.g. from a process sentinel).
You can make it reliable with the use of the new
`pre-redisplay-function' hook (instead of post-command-hook), which
I just added yesterday.
Of course, making it reliable doesn't mean it's not an omission.
I tend to agree that it would be good to provide access to that info
|[Prev in Thread]||Current Thread||[Next in Thread]|