From: Bastien <bzg@altern.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16497@debbugs.gnu.org
Subject: bug#16497: 24.3.50; `move-to-column' ignores invisible text at the beginning of the line, which create problems when using string-rectangle
Date: Mon, 20 Jan 2014 19:22:51 +0100 [thread overview]
Message-ID: <87d2jmjyx0.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jwvzjmq7cc6.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 20 Jan 2014 13:14:37 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> It's probably due to the post-command processing which tries to move
> point outside of invisible regions and to pretend that invisible regions
> don't exist at all (and paying attention to stickiness so that it
> prefers text positions where `invisible' won't be inherited).
>
> So moving from "before a" to "before b" ends up moving to "before c"
> so that C-f from "before a" moves visually by one char (to "before c").
Thanks -- you nearly lost me here!
Should not this be considered a bug?
I don't have a real-world use case where this would happen,
but it is obviously wrong and suggests other similar errors
could bite the user.
--
Bastien
next prev parent reply other threads:[~2014-01-20 18:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 16:26 bug#16497: 24.3.50; `move-to-column' ignores invisible text at the beginning of the line, which create problems when using string-rectangle Bastien Guerry
2014-01-19 17:11 ` Eli Zaretskii
2014-01-20 9:22 ` Bastien
2014-01-20 15:38 ` Eli Zaretskii
2014-01-20 16:25 ` Bastien
[not found] ` <<83eh42iry6.fsf@gnu.org>
2014-01-20 18:10 ` Drew Adams
2014-01-19 20:48 ` Stefan Monnier
2014-01-20 9:11 ` Bastien
2014-01-20 15:41 ` Eli Zaretskii
2014-01-20 16:50 ` Bastien
2014-01-20 18:14 ` Stefan Monnier
2014-01-20 18:22 ` Bastien [this message]
2014-01-20 19:10 ` Stefan Monnier
2014-01-20 20:55 ` Bastien
2014-01-20 19:19 ` Eli Zaretskii
[not found] <<87ob38gcp1.fsf@bzg.ath.cx>
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=87d2jmjyx0.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=16497@debbugs.gnu.org \
--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 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.