unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 09 Apr 2015 18:06:01 +0300	[thread overview]
Message-ID: <831tjtfijq.fsf@gnu.org> (raw)
In-Reply-To: <8761954apb.fsf@gnu.org>

> From: Tassilo Horn <tsdh@gnu.org>
> Date: Thu, 09 Apr 2015 16:50:56 +0200
> 
> Sometimes it occurs to me that `blink-cursor-mode' stops blinking the
> cursor for some time.  That temporary stop might also occur in the
> off-phase so that there's no visible cursor anymore.  As soon as I press
> some key, the blinking starts again.  But just now in some specific
> buffer, it'll blink twice and then disappear until I press a key again.

It generally means that some other time, probably an idle time, takes
more than 0.5 sec to do its job.

> Then I added a (message "BLINK") as the first form in
> `blink-cursor-timer-function'.  And strangely, when the blinking stops
> for whatever reason, I can still see BLINK [53 times] with increasing
> repetition count in *Messages*.

The contents of "*Messages*" is modified by Lisp code, while to see
the cursor blinking you need to have a redisplay cycle.  Emacs will
not enter redisplay if it has something else to do, like some timer
that is ripe and needs to be run.

> So the problem seems to be that
> 
>   (internal-show-cursor nil (not (internal-show-cursor-p)))
> 
> stops working for some unknown reason.

No, I don't think this conclusion is correct, see above.

> Then I changed my message to
> 
>   (message "BLINK: %s" (internal-show-cursor-p))
> 
> and now I get alternating
> 
>   BLINK: nil
>   BLINK: t
> 
> sequences even though the cursor has stopped blinking already.  So I
> guess the problem is that no redisplay is performed which would make the
> visibility toggle of the cursor effective, and thus don't notice that
> the cursor should have been visible/invisible for the last half of a
> second.

Exactly.

> Of course, that doesn't happen always and I've not been able reproduce
> it using emacs -Q.  I think I get this problem most frequently when
> editing large LaTeX files with AUCTeX but I think I got it also in some
> other buffers already, so this observation might only show that I'm
> writing LaTeX documents a good bit of my time.

Look at your other times, and find the one which takes too much time
for doing its job.





  reply	other threads:[~2015-04-09 15:06 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 [this message]
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
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=831tjtfijq.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).