From: Eli Zaretskii <eliz@gnu.org>
To: monnier@IRO.UMontreal.CA
Cc: michael_heerdegen@web.de, 17392@debbugs.gnu.org
Subject: bug#17392: 24.3.90; cursor blinks faster and faster
Date: Wed, 14 May 2014 17:59:55 +0300 [thread overview]
Message-ID: <834n0spfro.fsf@gnu.org> (raw)
In-Reply-To: <838uq5ozaz.fsf@gnu.org>
> Date: Wed, 14 May 2014 05:43:16 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: michael_heerdegen@web.de, 17392@debbugs.gnu.org
>
> > How 'bout: the list contains two timers, we copy it, then run the first
> > which removes the second, then run the second which doesn't find itself
> > in the list.
>
> I thought about this, but (a) I don't see where the blink-cursor timer
> removes any other timers
Actually, this is inaccurate: blink-cursor-timer-function, which runs
off a regular (non-idle) timer, sometimes calls blink-cursor-suspend,
which cancels the blink-cursor-idle-timer.
But this looks perfectly normal, and indeed if Michael's advice runs
when the idle timer expired, it might find that the idle timer that
runs was already deleted from timer-idle-list, because we invoke the
timers from a copy of the list. If this is what happens, then what
Michael's code reveals is an artifact of a perfectly normal and
expected operation. I cannot see how this could cause more than one
blink-cursor-idle-timer be in the list at the same time.
> (b) I don't see why this scenario would be a problem that could lead
> to the issue in point in the first place.
So this still stands.
next prev parent reply other threads:[~2014-05-14 14:59 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 1:44 bug#17392: 24.3.90; cursor blinks faster and faster Michael Heerdegen
2014-05-03 18:33 ` Michael Heerdegen
2014-05-03 22:29 ` Michael Heerdegen
2014-05-05 12:25 ` Stefan Monnier
2014-05-05 13:14 ` Lennart Borgman
2014-05-05 20:17 ` Michael Heerdegen
2014-05-05 23:07 ` Michael Heerdegen
2014-05-05 23:30 ` Michael Heerdegen
2014-05-06 21:20 ` Michael Heerdegen
2014-05-07 2:02 ` Stefan Monnier
2014-05-07 2:14 ` Michael Heerdegen
2014-05-07 13:15 ` Stefan Monnier
2014-05-08 16:52 ` Michael Heerdegen
2014-05-08 17:04 ` Eli Zaretskii
2014-05-08 17:09 ` Lennart Borgman
2014-05-08 17:42 ` Michael Heerdegen
2014-05-08 18:40 ` Lennart Borgman
2014-05-10 10:34 ` Michael Heerdegen
2014-05-10 11:06 ` Eli Zaretskii
2014-05-10 11:40 ` Michael Heerdegen
2014-05-10 12:32 ` Eli Zaretskii
2014-05-10 16:16 ` Eli Zaretskii
2014-05-11 11:09 ` Michael Heerdegen
2014-05-11 16:40 ` Eli Zaretskii
2014-05-13 16:04 ` Michael Heerdegen
2014-05-13 17:50 ` Eli Zaretskii
2014-05-13 17:58 ` Lennart Borgman
2014-05-13 18:14 ` Eli Zaretskii
2014-05-13 18:25 ` Lennart Borgman
2014-05-13 18:44 ` Eli Zaretskii
2014-05-13 18:50 ` Lennart Borgman
2014-05-13 19:47 ` Eli Zaretskii
2014-05-13 20:10 ` Lennart Borgman
2014-05-14 2:40 ` Eli Zaretskii
2014-05-13 20:22 ` Stefan Monnier
2014-05-14 2:43 ` Eli Zaretskii
2014-05-14 14:59 ` Eli Zaretskii [this message]
2014-05-14 15:36 ` Michael Heerdegen
2014-05-14 16:00 ` Michael Heerdegen
2014-05-14 16:13 ` Eli Zaretskii
2014-05-14 17:23 ` Michael Heerdegen
2014-05-14 18:15 ` Eli Zaretskii
2014-05-14 19:11 ` Lennart Borgman
2014-05-14 19:30 ` Eli Zaretskii
2014-05-14 20:17 ` Lennart Borgman
2014-05-15 2:40 ` Eli Zaretskii
2014-05-15 3:31 ` Lennart Borgman
2014-05-15 17:04 ` Eli Zaretskii
2014-05-15 19:11 ` Lennart Borgman
2014-05-15 19:17 ` Eli Zaretskii
2014-05-15 20:22 ` Lennart Borgman
2014-05-16 5:30 ` Eli Zaretskii
2014-05-16 8:41 ` Lennart Borgman
2014-05-15 20:34 ` Glenn Morris
2014-05-15 20:44 ` Lennart Borgman
2014-05-07 2:27 ` Michael Heerdegen
2014-05-07 3:01 ` Michael Heerdegen
2014-05-07 13:57 ` Nicolas Richard
2014-05-18 13:05 ` Stefan Monnier
2014-05-18 13:41 ` Michael Heerdegen
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=834n0spfro.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17392@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@IRO.UMontreal.CA \
/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.