Re: Tramp with global-auto-revert-mode.

[Kim F. Storm]

Stefan Monnier <address@hidden> writes:

> >> If a timer does something like accept-process-output, stopping other
> >> timers would probably be a mistake.
> > But it seems quite bogus for a timer to do that ...  as it blocks
> > interactive use.
> > IMO, timers should be "fast".
> 
> Agreed, but accept-process-output is not always slow and we don't always get
> to choose.  I've hacked my Emacs to signal an error if accept-process-output
> is called (without timeout) with inhibit-quit set to non-nil and discovered
> that some package (IIRC, flyspell) does exactly that.  Of course, ispell
> is a local process that always responds immeditely, right?
> Anyway: how could flyspell do its job without calling 
> accept-process-output from a timer or a post-command-hook?

timer-event-handler sets inhibit-quit to t before calling the timer's
function, so if that function calls accept-process-output, it should
explicitly set inhibit-quit to nil -- but how does that affect the 
timer system ?

-- 
Kim F. Storm <address@hidden> http://www.cua.dk