unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 28 Oct 2019 19:00:57 +0200	[thread overview]
Message-ID: <831ruwst2u.fsf@gnu.org> (raw)
In-Reply-To: <87o8y0986h.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  28 Oct 2019 16:55:02 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 28 Oct 2019 16:55:02 +0100
> Cc: Phil Sainty <psainty@orcon.net.nz>, 37875@debbugs.gnu.org
> 
> Does anybody know why run-with-timer was added?  I think we should
> obsolete one or the other, and I think run-at-time has the best name.

  $ fgrep run-with-timer lisp/ChangeLog.*
  lisp/ChangeLog.17:15268:     (desktop-auto-save-set-timer): Replace `run-with-timer' with
  lisp/ChangeLog.6:2135:       (run-with-timer): Just call run-at-time.
  lisp/ChangeLog.6:2797:       * timer.el (run-with-timer): Set repetition interval.
  lisp/ChangeLog.6:2925:       (run-with-timer): Renamed from run-after-delay.
  lisp/ChangeLog.6:2926:       (run-at-time, run-with-timer): Return the timer.

  $ fgrep run-after-delay lisp/ChangeLog.*
  lisp/ChangeLog.6:2935:       (run-after-delay): New function.

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).

Does that answer your question?

(I don't really understand what would we gain by obsoleting such a
popular function.)





  reply	other threads:[~2019-10-28 17:00 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 [this message]
2019-10-29 11:20       ` Lars Ingebrigtsen
2019-10-29 11:34         ` Phil Sainty
2019-10-29 12:31         ` Eli Zaretskii
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=831ruwst2u.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).