Re: x-autoselect-window

["Eli Zaretskii" <eliz@is.elta.co.il>]

> From: gerd.moellmann@t-online.de (Gerd Moellmann)
> Date: 16 Feb 2002 19:25:10 +0100
> 
> > Is it possible that the frame-based redisplay needs something else?
> 
> I don't think so.  The frame- vs. window-based thing should play a
> role only in the display update phase, i.e., after glyph matrices
> for windows have been built.  This case sounds more as if matrices for
> some windows haven't been built.

More digging reveals that redisplay isn't called.  Once it _is_ called
(e.g., by just waiting for about 2 minutes, to let the sit-for in the
command loop to do its thing), the selected window is correctly
updated.

What drives me crazy is that "C-x o", which basically just calls
Fselect_window, does cause redisplay to be called.  The only
difference between "C-x o" and the code I'm debugging is that "C-x o"
produces an input event, while the code I'm looking into does not.
Does that ring a bell perhaps?

> It might also be interesting to look at the trace
> output that Emacs prints when built with -DGLYPH_DEBUG and turned on
> with M-x trace-redisplay.

I didn't try that, but I bet it will show redisplay isn't called.  I
put a breakpoint in redisplay_internal, and it wasn't hit until 2
minutes or so later.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel