GNU bug report logs - #21468
24.5; When next-line (visual) crosses overlay with before-string="\n" point goes to column 0

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: 21468 <at> debbugs.gnu.org
Subject: bug#21468: 24.5; When next-line (visual) crosses overlay with before-string="\n" point goes to column 0
Date: Sat, 10 Oct 2015 20:09:33 +0300

> Date: Sat, 10 Oct 2015 12:51:06 -0400
> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
> Cc: 21468 <at> debbugs.gnu.org
> 
> On Sat, Oct 10, 2015 at 10:20 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> >> Date: Sat, 10 Oct 2015 09:37:43 -0400
> >> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
> >> Cc: 21468 <at> debbugs.gnu.org
> >>
> >> The 2nd case
> >>
> >>    emacs -Q -l 21468-overlay.el -f 21468-test-eol-col-movement
> >>
> >> then hit C-e C-n. Point lands at the end of line 8 instead of line 8,
> >> column 33 which is what happens when there is no overlay.
> >
> > This is not a bug: vertical-motion doesn't know about the 'cursor'
> > property, so it works as if the property didn't exist.
> 
> Okay, that makes sense, but it means this approach is worse than
> overlayed newlines for magit.

I don't think so.  I think a casual mismatch in a column while moving
through a buffer, and in marginal cases at that, is not a big deal.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.