From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com
Cc: emacs-devel@gnu.org
Subject: Re: call-process should not block process filters from running
Date: Tue, 04 Jul 2023 19:38:38 +0300 [thread overview]
Message-ID: <833523ljht.fsf@gnu.org> (raw)
In-Reply-To: <87y1jvokcx.fsf@catern.com> (sbaugh@catern.com)
> From: sbaugh@catern.com
> Date: Tue, 04 Jul 2023 09:51:42 -0400
>
> >Timer functions should also avoid calling functions that cause Emacs to
> >wait, such as ‘sit-for’ (*note Waiting::). This can lead to
> >unpredictable effects, since other timers (or even the same timer) can
> >run while waiting.
>
> But it seems that the "(or even the same timer)" part is not true in
> practice. From looking at timer-event-handler this makes sense - it
> looks like we remove the timer from timer-list before running it. So
> timers don't run concurrently with themselves. Which since it's already
> the case, we might as well formalize, since it's useful for Lisp
> programmers...
You cannot formalize that because a timer function can activate the
same timer again.
Also, there's a window before timer-event-handler removes the time
during which the same timer can still run.
Basically, once you allow to run Lisp, all bets are off...
next prev parent reply other threads:[~2023-07-04 16:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 21:55 call-process should not block process filters from running Spencer Baugh
2023-06-28 11:39 ` Mattias Engdegård
2023-06-28 11:56 ` Po Lu
2023-06-28 12:08 ` Spencer Baugh
2023-06-28 13:17 ` Po Lu
2023-06-28 12:52 ` Eli Zaretskii
2023-06-28 13:27 ` Spencer Baugh
2023-06-28 13:34 ` Eli Zaretskii
2023-07-01 18:24 ` Spencer Baugh
2023-07-01 18:59 ` Eli Zaretskii
2023-07-01 19:17 ` Spencer Baugh
2023-07-02 5:45 ` Eli Zaretskii
2023-07-03 0:02 ` sbaugh
2023-07-03 10:00 ` Po Lu
2023-07-03 17:53 ` sbaugh
2023-07-03 18:51 ` Eli Zaretskii
2023-07-03 20:28 ` sbaugh
2023-07-04 4:12 ` Po Lu
2023-07-04 11:25 ` Eli Zaretskii
2023-07-04 12:42 ` sbaugh
2023-07-04 13:42 ` Michael Albinus
2023-07-04 14:16 ` sbaugh
2023-07-05 6:36 ` Michael Albinus
2023-07-04 11:10 ` Eli Zaretskii
2023-07-04 12:20 ` sbaugh
2023-07-04 13:09 ` Eli Zaretskii
2023-07-04 13:37 ` sbaugh
2023-07-04 13:25 ` Po Lu
2023-07-04 1:04 ` sbaugh
2023-07-04 4:09 ` Po Lu
2023-07-04 12:27 ` sbaugh
2023-07-04 13:22 ` Po Lu
2023-07-04 13:51 ` sbaugh
2023-07-04 16:38 ` Eli Zaretskii [this message]
2023-07-04 16:53 ` sbaugh
2023-07-04 17:14 ` Eli Zaretskii
2023-07-04 16:49 ` Dmitry Gutov
2023-07-04 18:12 ` sbaugh
2023-07-05 18:53 ` Dmitry Gutov
2023-07-06 2:24 ` sbaugh
2023-07-06 8:06 ` Michael Albinus
2023-07-08 15:54 ` sbaugh
2023-07-09 9:04 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=833523ljht.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sbaugh@catern.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.