From: Eli Zaretskii <eliz@gnu.org>
To: Campbell Barton <ideasman42@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Possible support for buffer local idle timers?
Date: Tue, 21 Sep 2021 13:43:59 +0300 [thread overview]
Message-ID: <838rzqyzrk.fsf@gnu.org> (raw)
In-Reply-To: <CAEcf3NzTqq1OStzu4t2vQosDz+4YwL_sipWhhgJRAnrW0mE3WA@mail.gmail.com> (message from Campbell Barton on Tue, 21 Sep 2021 20:19:44 +1000)
> From: Campbell Barton <ideasman42@gmail.com>
> Date: Tue, 21 Sep 2021 20:19:44 +1000
> Cc: emacs-devel@gnu.org
>
> On Tue, Sep 21, 2021 at 4:07 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > Date: Tue, 21 Sep 2021 10:36:05 +1000
> > > From: Campbell Barton <ideasman42@gmail.com>
> > >
> > > > . does the timer start measuring idle time only when the buffer is
> > > > the current buffer, or regardless of that?
> > >
> > > would just go with default behavior of global idle timers since a user
> > > switching buffers will typically reset idle timers.
> >
> > What do you mean by "reset timers" here?
>
> I assume that the the act of switching the buffer will cause Emacs not
> to be idle, so after switching buffers idle timers will begin to run
> again as their deadlines are met.
No, that is not necessarily true. "Idle" means there's no input for
Emacs to process, but it doesn't mean Emacs is not doing anything. It
could run some timer-related code which switches buffers, for example.
next prev parent reply other threads:[~2021-09-21 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 13:49 Possible support for buffer local idle timers? Campbell Barton
2021-09-20 15:30 ` Eli Zaretskii
2021-09-20 15:50 ` Campbell Barton
2021-09-20 16:08 ` Eli Zaretskii
2021-09-21 0:36 ` Campbell Barton
2021-09-21 6:07 ` Eli Zaretskii
2021-09-21 6:16 ` Lars Ingebrigtsen
2021-09-21 10:19 ` Campbell Barton
2021-09-21 10:43 ` Eli Zaretskii [this message]
2021-09-25 7:26 ` Campbell Barton
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=838rzqyzrk.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).