all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.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 12:20:38 +0100	[thread overview]
Message-ID: <87wocn23y1.fsf@gnus.org> (raw)
In-Reply-To: <831ruwst2u.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 28 Oct 2019 19:00:57 +0200")

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.

> Does that answer your question?

Not really -- I wondered why there were two functions (run-with-timer
and run-at-time) that are identical.

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

It could be made into a defalias at least -- the run-at-time doc string
is much better than the run-with-timer one.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-29 11:20 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wocn23y1.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37875@debbugs.gnu.org \
    --cc=eliz@gnu.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 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.