From: Eli Zaretskii <eliz@gnu.org>
To: ndame <emacsuser@freemail.hu>
Cc: 39668@debbugs.gnu.org
Subject: bug#39668: 26.2; timer-list and timer-idle-list are undocumented in the Elisp manual
Date: Tue, 18 Feb 2020 21:26:12 +0200 [thread overview]
Message-ID: <83r1yrlmsr.fsf@gnu.org> (raw)
In-Reply-To: <AySsWA.U0rWxUznjc0.4xlRSKDre0qvSCR7Qm03@freemail.hu> (message from ndame on Tue, 18 Feb 2020 18:45:56 +0000 (GMT))
> Date: Tue, 18 Feb 2020 18:45:56 +0000 (GMT)
> From: ndame <emacsuser@freemail.hu>
> Cc: "39668@debbugs.gnu.org" <39668@debbugs.gnu.org>
>
> I needed to access the list of the active timers from an elisp program.
> Since timers are available from elisp, the list of timers should be
> available too, like the list of buffers, etc.
>
> I was suprised that I did not find this in the manual. Since timers are
> part of the public elisp api, I expect timer lists also to be part of the
> public api.
We don't describe those lists intentionally, because messing with them
can produce unexpected results. Think about that: while you are
modifying the list of timers, some timer might expire, and Emacs will
run it, and modify the list as result. (We do have protection from at
least the simplest forms of such races, but still, we don't like to
have Lisp programs manipulate those lists.)
Why do you need to access the active timers?
next prev parent reply other threads:[~2020-02-18 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 17:54 bug#39668: 26.2; timer-list and timer-idle-list are undocumented in the Elisp manual ndame
2020-02-18 18:35 ` Eli Zaretskii
2020-02-18 18:45 ` ndame
2020-02-18 19:26 ` Eli Zaretskii [this message]
2020-02-18 19:36 ` ndame
2020-02-18 19:57 ` Eli Zaretskii
2020-02-18 20:04 ` ndame
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=83r1yrlmsr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39668@debbugs.gnu.org \
--cc=emacsuser@freemail.hu \
/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.