Re: read-event and unexpected buffer changes

[Stefan Monnier]

>       (let ((event (let (unread-command-events) (read-event nil nil 0.1))))
>         (when (and event (not (ignore-errors (dbus-check-event event))))
>           (setq unread-command-events
>                 (append unread-command-events (list event)))))))

Why not use sit-for?

> But because of this `read-event' call, the buffer is "recentered to the
> top" and I finally see this instead:

The only expected side-effect is a redisplay (which could also trigger
things like jit-lock).

> Hint?

Sorry,


        Stefan