From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 13559@debbugs.gnu.org
Subject: bug#13559: 24.3.50; mysterious, uncalled-for point movement when exit minibuffer
Date: Sat, 26 Jan 2013 10:18:18 -0800 [thread overview]
Message-ID: <F5726B5F27A84727824626505E0B190C@us.oracle.com> (raw)
In-Reply-To: <83bocbke1r.fsf@gnu.org>
> > Sorry, but I cannot give a recipe to repro this yet.
> >
> > Somehow, it is suddenly the case (with my setup, but only with
> > recent builds, perhaps just the latest I have, 2013-01-25 -
> > that's where I noticed it) that with even something as simple as
> > M-x forward-char or M-: (forward-char), and even if I use C-g to
> > cancel such (e.g., just M-x C-g), point gets moved to another
> > location. I need not hit C-g - the same thing happens with
> > M-x forward-char RET.
>
> Can you try reproducing this from "emacs -Q"?
No, I don't think so. Not until I find out more about it. If & when I do, I'll
let you know.
> I'm guessing that some redisplay change made lately goofed, but it's
> hard to look for it without a recipe.
With luck more people will run into it and we'll learn more. Sooner or later we
will perhaps be able to repro it simply, from emacs -Q.
For now, the bug report is just a heads-up. Perhaps it will help as is, ringing
a bell for someone who made recent changes. So far, I've seen this in a build
from 1/25, but not yet in a build from 1/22. (Doesn't mean I won't encounter it
with 1/22, just saying that's what I've seen so far.)
next prev parent reply other threads:[~2013-01-26 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 17:44 bug#13559: 24.3.50; mysterious, uncalled-for point movement when exit minibuffer Drew Adams
2013-01-26 18:13 ` Eli Zaretskii
2013-01-26 18:18 ` Drew Adams [this message]
2014-02-10 4:45 ` 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=F5726B5F27A84727824626505E0B190C@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13559@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.