From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 20285@debbugs.gnu.org
Subject: bug#20285: 25.0.50; blink-cursor-mode sometimes stops blinking
Date: Sat, 11 Apr 2015 09:25:39 +0300 [thread overview]
Message-ID: <83h9snrxjw.fsf@gnu.org> (raw)
In-Reply-To: <874monemf7.fsf@gnu.org>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: 20285@debbugs.gnu.org
> Date: Fri, 10 Apr 2015 22:52:12 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > Maybe we should have a mechanism to force redisplay once in a while
> >> > even if Emacs has something to do, and blink-cursor-mode could then
> >> > activate that mechanism.
> >>
> >> I can't read your brain but wouldn't it be possible (but unlikely)
> >> that this mechanism always forces a redisplay when the cursor is in
> >> the invisible state?
> >
> > Not if the time interval is chosen as to make the probability of this
> > low enough.
>
> Yes, but what if different things request different redisplay intervals?
> E.g., `blink-cursor-mode' requests an interval of 1.25, and some other
> thing requests an interval of 1.0? 1.0 is a bad interval for b-c-m's
> sake, so that mechanism can't just use the shortest interval.
Yes, the shortest interval is indeed not the best policy. But it's
not the only one that we could use, I think.
next prev parent reply other threads:[~2015-04-11 6:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 14:50 bug#20285: 25.0.50; blink-cursor-mode sometimes stops blinking Tassilo Horn
2015-04-09 15:06 ` Eli Zaretskii
2015-04-09 16:07 ` Eli Zaretskii
2015-04-10 7:46 ` Tassilo Horn
2015-04-10 7:58 ` Eli Zaretskii
2015-04-10 9:28 ` Tassilo Horn
2015-04-10 12:42 ` Eli Zaretskii
2015-04-10 13:13 ` Tassilo Horn
2015-04-10 13:28 ` Eli Zaretskii
2015-04-10 13:32 ` Eli Zaretskii
2015-04-10 14:13 ` Tassilo Horn
2015-04-10 17:32 ` Eli Zaretskii
2015-04-10 20:52 ` Tassilo Horn
2015-04-11 6:25 ` Eli Zaretskii [this message]
2015-04-10 18:24 ` Stefan Monnier
2015-04-10 18:42 ` Eli Zaretskii
2015-04-10 20:21 ` Tassilo Horn
2015-04-10 21:50 ` Stefan Monnier
2015-04-11 5:54 ` Tassilo Horn
2015-04-11 7:34 ` Eli Zaretskii
2015-04-11 11:34 ` Eli Zaretskii
2015-04-11 11:49 ` Tassilo Horn
2015-04-11 12:39 ` Tassilo Horn
2015-04-11 14:45 ` Eli Zaretskii
2015-04-11 19:24 ` Tassilo Horn
2015-04-11 19:45 ` Eli Zaretskii
2015-04-11 20:17 ` Tassilo Horn
2015-04-11 14:02 ` Stefan Monnier
2015-04-11 14:30 ` Tassilo Horn
2015-04-11 14:48 ` Eli Zaretskii
2015-04-11 15:14 ` Eli Zaretskii
2015-04-12 4:05 ` Stefan Monnier
2015-04-11 6:30 ` Eli Zaretskii
2022-04-28 10:50 ` Lars Ingebrigtsen
2022-04-28 11:48 ` Tassilo Horn
2022-04-28 11:51 ` 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
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=83h9snrxjw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20285@debbugs.gnu.org \
--cc=tsdh@gnu.org \
/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).