Chris Moore <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Kim F. Storm) writes: > >> If you just break it in the debugger a few times and look at a backtrace. >> If it is inside a select call, walk up the stack to see what the timeout >> is - and where it is set. > > Thanks for your help. I found the 0.5 second timer in w3m.el:
Great! Could you report this to the w3m maintainers. > > (run-at-time 0.5 nil > > This change stops the 'jumping back' behaviour that the original > reported was complaining of, but I expect it breaks something else - > I've just disabled the call which is causing the jump-back without > understanding why or whether it's needed: > > ------------------------------------------------------------------------ > --- Backup/w3m.el.~1~ 2007-01-02 09:50:03.000000000 +0100 > +++ w3m.el 2007-01-05 15:27:40.000000000 +0100 > @@ -7287,7 +7287,7 @@ > (setq w3m-modeline-title-timer nil) > (when (eq (selected-window) > (get-buffer-window buffer)) > - (w3m-force-window-update))))) > + '(w3m-force-window-update))))) > (current-buffer)))))) > > ;;;###autoload > ------------------------------------------------------------------------ -- Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
