From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: michael_heerdegen@web.de, jonas@bernoul.li, 19200@debbugs.gnu.org
Subject: bug#19200: Point adjustemnt moves *into* invisible text
Date: Tue, 22 Mar 2016 20:52:57 +0200 [thread overview]
Message-ID: <83egb24a5y.fsf@gnu.org> (raw)
In-Reply-To: <jwvoaa6pe49.fsf-monnier+Inbox@gnu.org> (message from Stefan Monnier on Tue, 22 Mar 2016 14:36:10 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 19200@debbugs.gnu.org, michael_heerdegen@web.de, jonas@bernoul.li
> Date: Tue, 22 Mar 2016 14:36:10 -0400
>
> > So what exactly is this bug about?
>
> There are 2 odd behaviors:
> - point adjustment doesn't bring us to position 3 after C-n
Why is that a problem? Position 3 is invisible, so we shouldn't
expect to end up with point there.
> - M-: (point) has the side-effect of bringing us to position 3
> My guess here is that after the M-: command, at the end of
> command_loop_1, last_point_position refers to a position in another
> buffer (i.e. in the minibuffer), so it thinks there was a movement and
> hence re-runs adjust_point_for_property, which this time gets it right.
Maybe. If this is the bug to solve, I could look into it. But your
original reports said this is actually the correct position of point,
a claim which I don't understand.
next prev parent reply other threads:[~2016-03-22 18:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 22:22 bug#19200: Point adjustemnt moves *into* invisible text Stefan Monnier
2016-03-20 22:58 ` Michael Heerdegen
2016-03-21 1:21 ` Stefan Monnier
2016-03-21 2:15 ` Michael Heerdegen
2016-03-21 2:23 ` Michael Heerdegen
2016-03-21 18:30 ` Eli Zaretskii
2016-03-21 12:08 ` Stefan Monnier
2016-03-21 14:52 ` Michael Heerdegen
2016-03-21 15:36 ` Stefan Monnier
2016-03-21 15:54 ` Michael Heerdegen
2016-03-21 18:08 ` Stefan Monnier
2016-03-21 18:28 ` Eli Zaretskii
2016-03-21 19:24 ` Michael Heerdegen
2016-03-21 19:40 ` Eli Zaretskii
2016-03-21 20:10 ` Michael Heerdegen
2016-03-21 20:21 ` Michael Heerdegen
2016-03-21 20:43 ` Stefan Monnier
2016-03-22 16:39 ` Eli Zaretskii
2016-03-22 18:36 ` Stefan Monnier
2016-03-22 18:52 ` Eli Zaretskii [this message]
2016-03-23 2:13 ` Stefan Monnier
2016-03-23 15:15 ` Eli Zaretskii
2016-03-23 15:32 ` Stefan Monnier
2016-03-23 15:42 ` Eli Zaretskii
2016-03-23 16:10 ` Stefan Monnier
2016-03-31 17:17 ` Eli Zaretskii
2016-03-31 18:04 ` Stefan Monnier
2016-03-31 23:32 ` Michael Heerdegen
2016-03-26 21:49 ` bug#19200: Point adjustment " John Wiegley
2016-03-21 18:31 ` bug#19200: Point adjustemnt " Eli Zaretskii
2016-03-21 18:50 ` Michael Heerdegen
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=83egb24a5y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19200@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).