From: Drew Adams <drew.adams@oracle.com>
To: Harald Hanche-Olsen <hanche@math.ntnu.no>, emacs-devel@gnu.org
Subject: RE: How did that happen?
Date: Wed, 8 Oct 2014 06:26:34 -0700 (PDT) [thread overview]
Message-ID: <df7268a3-3122-4a74-94a6-5ba8e894c686@default> (raw)
In-Reply-To: <20141008.134126.986137492679816828.hanche@math.ntnu.no>
> I just had emacs getting into this strange state: Everything seemed
> normal, except for one little thing: The cursor would jump to the
> beginning of the line after I inserted any character. This happened
> everywhere, including in the minibuffer.
>
> Needless to say, this made emacs difficult to use to say the least.
> The only thing I could think of checking was if something had gotten
> into after-change-functions, but its value was as expected:
> (mew-draft-dynamic-highlight t), global value nil. (What fun to type
> stuff like C-h v -retfa C-e -ahc C-e nuf TAB in order to
> investigate!)
>
> Unfortunately, I haven't the faintest idea how to trigger this
> behaviour, or I would submit a bug report right away.
>
> Does anyone here have any notion what could possibly trigger this
> behaviour? Or suggestions for what I might try, should I encounter
> it again? I had to terminate that instance – it is just too painful to
> run two instances of emacs simultaneously, or I might have kept it
> around so I could investigate it some more.
My wild guess is that an error causes the current operation to be
interrupted, and point is returned to bol (where it was sent by
part of the operation). If it happens after each insertion, perhaps
it occurs during a function on `post-command-hook'.
You might not be able to use `debug-on-entry' for those functions,
but if it happens again you could at least do a binary search to
determine which of them is problematic, and then, say, use `message'
to track its progress.
prev parent reply other threads:[~2014-10-08 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 11:41 How did that happen? Harald Hanche-Olsen
2014-10-08 12:10 ` Andreas Schwab
2014-10-08 13:26 ` Drew Adams [this message]
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=df7268a3-3122-4a74-94a6-5ba8e894c686@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=hanche@math.ntnu.no \
/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).