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

[David Kastrup]

Kai Grossjohann <address@hidden> writes:

> Stefan Monnier <address@hidden> writes:
> 
> >> I do not see why global-auto-revert-mode should increase the
> >> probability of Tramp being recalled recursively.  It certainly
> >
> > Because it runs Tramp from a timer.  Timers can be run whenever Emacs is
> > waiting, i.e. it can happen when Tramp is waiting for the other end's
> > prompt to come up.
> 
> Eeek.
> 
> There is nothing in Tramp that anticipates such reentrant calls.
> 
> What should Tramp do with such calls?

Work properly if they are on a different connection.  Queue them if
they are on the same connection.  You don't need an explicit queue for
that, you can just sleep with accept-process-output and get woken up
at a time when there might nothing else be pending anymore.  I don't
think a timer gets rerun while it is sleeping on that.

When the code continues, you probably should check whether something
else that was scheduled beforehand has already done the job.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum