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 17:45:21 +0300 [thread overview]
Message-ID: <831tjqg1vi.fsf@gnu.org> (raw)
In-Reply-To: <87r3rqq1ny.fsf@gnu.org>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: monnier@IRO.UMontreal.CA, 20285@debbugs.gnu.org
> Date: Sat, 11 Apr 2015 14:39:45 +0200
>
> Tassilo Horn <tsdh@gnu.org> writes:
>
> >> If your Emacs is configured with --enable-checking='yes,glyphs', then
> >> you can invoke "M-x trace-redisplay RET", and see every entry to
> >> redisplay_internal announced on stderr.
> >
> > Ok, I'll try that out.
>
> Done that now and got output like
>
> redisplay_preserve_echo_area (12)
> redisplay_internal 0
> redisplay_internal 0
> redisplay_preserve_echo_area (8)
> redisplay_internal 0
> redisplay_preserve_echo_area (12)
> redisplay_internal 0
> redisplay_internal 0
> redisplay_preserve_echo_area (12)
> redisplay_internal 0
> redisplay_internal 0
That's what you should get; each "redisplay_internal 0" line is an
entry to redisplay.
> In general, I've been amazed how often redisplay is performed even
> though nothing has changed in neither the single window containing the
> buffer with my latex doc nor the minibuffer. Ten times a second is very
> likely, maybe even more.
Really? Is that in "emacs -Q"? I get only 20 entries to redisplay,
every 0.5 sec, one each for every toggle of the blinking cursor, and
after those it stops.
I can only understand a much more frequent redisplay if you have a lot
of timers, or a high-frequency timer. When a timer fires, we call
redisplay, AFAIR.
> Then I compiled my latex doc to generate some stress. Every compile
> takes about a good minute. That used to work without blinking
> interruption at least four times, but with the fifth time, out of
> sudden, it stuck after
>
> redisplay_internal 0
I'm guessing that your LaTeX compilation is via "M-x compile" or a
similar async subprocess. If so, whether or not redisplay is called
depends on the speed the compilation process emits stuff that Emacs
reads. If the subprocess outputs a lot of stuff, it will have the
same effect as high-speed keyboard input -- in both cases Emacs will
not enter redisplay until it's idle.
> and would not start anymore until my latex document was compiled and
> AUCTeX echoed "LaTeX: successfully formatted {293} pages". That seems
> to have triggered the resume of redisplay.
Displaying an echo area message triggers redisplay.
> The redisplay pause was at least 20 to 30 seconds.
If there's no redisplay, you won't see the cursor blink.
next prev parent reply other threads:[~2015-04-11 14:45 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
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 [this message]
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=831tjqg1vi.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).