From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: michael_heerdegen@web.de, psainty@orcon.net.nz, 37875@debbugs.gnu.org
Subject: bug#37875: 27.0.50; `run-with-timer' not documented in (elisp)Timers
Date: Tue, 29 Oct 2019 14:31:46 +0200 [thread overview]
Message-ID: <83pnifpwb1.fsf@gnu.org> (raw)
In-Reply-To: <87wocn23y1.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 29 Oct 2019 12:20:38 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: michael_heerdegen@web.de, psainty@orcon.net.nz, 37875@debbugs.gnu.org
> Date: Tue, 29 Oct 2019 12:20:38 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > And if you look up the last match, you will see that run-after-delay
> > was added on the same day timer.el got rewritten using the internal
> > timers (before that -- oh horror! -- it worked by running an external
> > program which delivered a signal to Emacs when the time came).
>
> Geez.
Yeah.
> > Does that answer your question?
>
> Not really -- I wondered why there were two functions (run-with-timer
> and run-at-time) that are identical.
Because they aren't identical, see Phil's response. run-after-delay
was just that: it would run the function after a delay of SECS, and
that argument isn't supposed to be anything but a number of seconds to
wait from NOW.
next prev parent reply other threads:[~2019-10-29 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 18:38 bug#37875: 27.0.50; `run-with-timer' not documented in (elisp)Timers Phil Sainty
2019-10-23 7:01 ` Michael Heerdegen
2019-10-28 15:55 ` Lars Ingebrigtsen
2019-10-28 17:00 ` Eli Zaretskii
2019-10-29 11:20 ` Lars Ingebrigtsen
2019-10-29 11:34 ` Phil Sainty
2019-10-29 12:31 ` Eli Zaretskii [this message]
2019-10-29 12:37 ` Lars Ingebrigtsen
2019-10-29 12:41 ` Eli Zaretskii
2019-10-29 21:22 ` Lars Ingebrigtsen
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=83pnifpwb1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37875@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=psainty@orcon.net.nz \
/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).