From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: run-with-timer vs run-with-idle-timer
Date: Wed, 09 May 2018 22:21:35 +0300 [thread overview]
Message-ID: <837eocprcw.fsf@gnu.org> (raw)
In-Reply-To: <87tvrgbpys.fsf@gmail.com> (message from João Távora on Wed, 09 May 2018 20:15:23 +0100)
> From: João Távora <joaotavora@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Wed, 09 May 2018 20:15:23 +0100
>
> > An idle timer set for 600 seconds will run when ten minutes have
> > elapsed since the last user command was finished, even if subprocess
> > output has been accepted thousands of times within those ten minutes,
> > and even if there have been garbage collections and autosaves.
>
> Doesn't this contradict what you told me first? I.e doesn't this
> contradict the fact that this never returns?
>
> (catch 'done
> (run-with-idle-timer 600 nil (lambda () (throw 'done nil)))
> (while t (accept-process-output nil 0.1))) ; 6 thousand times
>
> or should the manual be saying "even if subprocesses output has been
> non-explictly accepted thousands of times"?
"Subprocess output" in that text doesn't include what
accept-process-output delivers, the text alludes to reading of
subprocess output via filter functions.
next prev parent reply other threads:[~2018-05-09 19:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 17:34 run-with-timer vs run-with-idle-timer João Távora
2018-05-09 18:10 ` Eli Zaretskii
2018-05-09 18:17 ` Eli Zaretskii
2018-05-09 18:40 ` João Távora
2018-05-09 18:59 ` Eli Zaretskii
2018-05-09 19:15 ` João Távora
2018-05-09 19:21 ` Eli Zaretskii [this message]
2018-05-09 19:34 ` João Távora
2018-05-09 20:00 ` Davis Herring
2018-05-09 20:18 ` João Távora
2018-05-10 11:46 ` Thien-Thi Nguyen
2018-05-10 12:28 ` João Távora
2018-05-10 18:50 ` Thien-Thi Nguyen
2018-05-11 10:39 ` João Távora
2018-05-11 11:05 ` João Távora
2018-05-12 17:57 ` Thien-Thi Nguyen
2018-05-12 17:37 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837eocprcw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).