From: Eli Zaretskii <eliz@gnu.org>
To: Campbell Barton <ideasman42@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Support for explicitly resetting the idle timer?
Date: Sat, 27 Nov 2021 12:54:19 +0200 [thread overview]
Message-ID: <83v90dzx5w.fsf@gnu.org> (raw)
In-Reply-To: <CAEcf3Ny3m2v-gACihNYkOcw5VakjLB0ifvesZFZmBo_ga_Ct7Q@mail.gmail.com> (message from Campbell Barton on Sat, 27 Nov 2021 21:21:29 +1100)
> From: Campbell Barton <ideasman42@gmail.com>
> Date: Sat, 27 Nov 2021 21:21:29 +1100
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> > > > Which code invokes set-window-vscroll, and what triggers that code?
> > >
> > > There is a while loop that uses (read-event) inside a `(track-mouse
> > > ...)` block that changes the scroll location and redraws.
> >
> > But that while loop is invoked by some binding of some mouse gesture,
> > no? That binding _is_ the "command" I meant.
>
> Ah, right. There is an interactive function bound to a key which runs
> track-mouse ... etc.
So now I wonder how come the idle timers run for you. Perhaps the
command you mention activates track-mouse and exits?
> Arguments could be made against this:
>
> - This could break existing packages that use long running commands
> and expect the idle timer to run.
While a command's code runs, idle timers cannot run, because timers
only run when Emacs is in its idle loop, waiting for some input.
Emacs only gets to the idle loop after a command exits and there's no
further input waiting for processing.
next prev parent reply other threads:[~2021-11-27 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 7:54 Support for explicitly resetting the idle timer? Campbell Barton
2021-11-27 8:02 ` Eli Zaretskii
2021-11-27 8:42 ` Campbell Barton
2021-11-27 9:01 ` Eli Zaretskii
2021-11-27 9:14 ` Campbell Barton
2021-11-27 10:11 ` Eli Zaretskii
2021-11-27 10:21 ` Campbell Barton
2021-11-27 10:54 ` Eli Zaretskii [this message]
2021-11-27 11:16 ` Campbell Barton
2021-11-27 11:33 ` 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
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=83v90dzx5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ideasman42@gmail.com \
/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).