From: William Rankin <william@bydasein.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39967@debbugs.gnu.org
Subject: bug#39967: 27.0.90; how to debug point moving erratically?
Date: Sat, 7 Mar 2020 23:47:24 +1000 [thread overview]
Message-ID: <9AB559B6-102A-4805-B7A1-55FB0195C9E2@bydasein.com> (raw)
In-Reply-To: <83mu8s9uw2.fsf@gnu.org>
> On 7 Mar 2020, at 11:06 pm, Eli Zaretskii <eliz@gnu.org> wrote:
>
> If this happens when Emacs is idle, the first suspect is some idle
> timer you have running. The variable timer-idle-list holds the list
> of the active idle timers, so look there for some hints.
This is what made me suspect jit-lock, because of the 5 sec idle timer
followed by jumping at 0.5 secs intervals.
Here's my timer list:
0.37 0.01 blink-cursor-timer-function
6.59 - undo-auto--boundary-timer
47.03 1.00 display-time-event-handler
* 0.00 t show-paren-function
* 0.50 t #f(compiled-function () #<bytecode 0x41903951> [jit-lock--antiblink-grace-timer jit-lock-context-fontify])
* 0.50 :repeat blink-cursor-start
* 1.00 t which-key--update
* 5.00 t jit-lock-stealth-fontify
Could the sporadic nature hint at the byte-compiled function that calls
jit-lock-context-fontify? (Also I see jit-lock-antiblink-grace is new
in 27.)
Of course there's also which-key, so I've turned that off for the time
being.
next prev parent reply other threads:[~2020-03-07 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 3:49 bug#39967: 27.0.90; how to debug point moving erratically? William Rankin
2020-03-07 8:00 ` Eli Zaretskii
2020-03-07 9:10 ` William Rankin
2020-03-07 11:04 ` Eli Zaretskii
2020-03-07 12:16 ` William Rankin
2020-03-07 13:06 ` Eli Zaretskii
2020-03-07 13:47 ` William Rankin [this message]
2020-03-07 15:32 ` Eli Zaretskii
2020-03-10 10:29 ` William Rankin
2022-02-02 18:24 ` Lars Ingebrigtsen
2022-02-04 5:06 ` Paul W. Rankin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05 6:34 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9AB559B6-102A-4805-B7A1-55FB0195C9E2@bydasein.com \
--to=william@bydasein.com \
--cc=39967@debbugs.gnu.org \
--cc=eliz@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 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.