all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 19:10:09 +1000	[thread overview]
Message-ID: <813C2B33-3356-4E32-A50D-4D4B9D2B3C74@bydasein.com> (raw)
In-Reply-To: <831rq4bnmc.fsf@gnu.org>



> On 7 Mar 2020, at 6:00 pm, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> How should I go about debugging this?
> 
> Find the feature you load/activate in your init files which causes
> this?

Hmm given the way it moves point, I would put money on this not being my
init. I'm not smart enough to write something that would work in such a
sporadic way.

I will of course endeavour to isolate my init away from the problem to
confirm it's not the culprit, but given that the problem only occurs
after hours of use and maybe a couple of times a week, this is going to
mean some time before I can give any useful confirmation.

Given the impending release of 27.1 maybe there are other avenues I can
check too?





  reply	other threads:[~2020-03-07  9:10 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 [this message]
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
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=813C2B33-3356-4E32-A50D-4D4B9D2B3C74@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.