From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 51094@debbugs.gnu.org
Subject: bug#51094: Check if run-with{-idle, }-timer needs to create a timer
Date: Fri, 08 Oct 2021 11:46:00 +0100 [thread overview]
Message-ID: <87a6jjn6af.fsf@tcd.ie> (raw)
In-Reply-To: <87a6jj97u1.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 08 Oct 2021 09:36:22 +0000")
Philip Kaludercic [2021-10-08 09:36 +0000] wrote:
> I have seen a few packages use run-with-timer or run-with-idle-timer,
> where the SECS parameter is configurable with a user option. When this
> timer doesn't repeat itself and it makes sense to set SECS to 0 when you
> want something to run immediately, I don't think it makes sense to
> create a timer object.
IIUC, the semantics of SECS=0 (alias nil) is not the same as eager
funcall, because timer functions are intended to be run asynchronously
in a separate command loop. So often what is meant by "now" is e.g. "as
soon as I quit the current active minibuffer".
I realise this patch does not touch run-at-time, but it's documented as
being interchangeable with run-with-timer, so the eager funcall sounds
like a breaking change.
If packages indeed want to run something immediately, why create a timer
at all? Or am I misunderstanding something?
Thanks,
--
Basil
next prev parent reply other threads:[~2021-10-08 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 9:36 bug#51094: Check if run-with{-idle,}-timer needs to create a timer Philip Kaludercic
2021-10-08 10:46 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-10-08 10:53 ` bug#51094: Check if run-with{-idle, }-timer " Lars Ingebrigtsen
2021-10-08 11:14 ` Lars Ingebrigtsen
2021-10-08 11:33 ` Philip Kaludercic
2021-10-08 12:29 ` Lars Ingebrigtsen
2021-10-08 11:03 ` Philip Kaludercic
2021-10-08 11:29 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-08 11:13 ` Eli Zaretskii
2021-10-08 11:08 ` Eli Zaretskii
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=87a6jjn6af.fsf@tcd.ie \
--to=bug-gnu-emacs@gnu.org \
--cc=51094@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=philipk@posteo.net \
/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.