Subject: bug#5372: Calling url-retrieve-synchronously in a timer

From: Stefan Monnier <[email-masked]>
Date: Wed, 13 Jan 2010 09:43:03 -0500

> It looks like url-retrieve-synchronously is not finished when run in a
> timer.  Is that expected behaviour?
> It looks like it hangs in accept-process-output.

It's not expected (for me anyway), but I'm not completely
surprised either.  Furthermore, it doesn't look like a good thing to
do anyway: timer code should not run for an indefinite amount of time,
so you should probably use url-retrieve instead.

        Stefan