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:57:51 +0200 [thread overview]
Message-ID: <83mu9fllc0.fsf@gnu.org> (raw)
In-Reply-To: <AySswA.fWC0tqhN05cg.PxJ5hPv8TJZERN2GDHN@freemail.hu> (message from ndame on Tue, 18 Feb 2020 19:36:08 +0000 (GMT))
> Date: Tue, 18 Feb 2020 19:36:08 +0000 (GMT)
> From: ndame <emacsuser@freemail.hu>
> Cc: "39668@debbugs.gnu.org" <39668@debbugs.gnu.org>
>
> > Why do you need to access the active timers?
>
> I wanted only to check the existing timers, not modify them,
> so I needed only read only access. I don't modify anything.
>
> I use this to avoid starting a timer if one is started already. So I just
> check the timer list for the function names if it already contains
> my function. If so then I don't start a timer, because it's already done.
>
> So the timer list eliminates the need of me haveing to store the timer in a variable,
> because the list tells me if it's already active.
There are other ways of doing that, but if you really need it for such
a rare use case, there's nothing wrong in reading the code.
next prev parent reply other threads:[~2020-02-18 19:57 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
2020-02-18 19:36 ` ndame
2020-02-18 19:57 ` Eli Zaretskii [this message]
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=83mu9fllc0.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.