Re: call-process should not block process filters from running

[Po Lu]

sbaugh@catern.com writes:

> AFAIK, timers don't run concurrently with themselves.  If a timer
> function is running, a second instance of that function won't run until
> the first one is finished.

That is untrue.  Instead, we discourage timer functions that are not
reentrant from calling functions which may check for input (such as
sit-for or read-event, and notably not call-process.)