GNU bug report logs -
#72420
set-goal-column misbehaves with a line-prefix and visual-line-mode
Previous Next
Full log
View this message in rfc822 format
> From: "Martin Edstrom" <meedstrom <at> runbox.eu>
> CC: "72420" <72420 <at> debbugs.gnu.org>
> Date: Wed, 07 Aug 2024 16:03:40 +0200 (CEST)
>
> > > From: "Martin Edstrom" <meedstrom <at> runbox.eu>
> > > CC: "72420" <72420 <at> debbugs.gnu.org>
> > > Date: Wed, 07 Aug 2024 14:07:45 +0200 (CEST)
> > >
> > > But, it's odd that visual-line-mode does not affect it for you - it does for me.
> > >
> > > If I leave visual-line-mode off, then I get the behavior I expect (i.e. set-goal-column at column 2 is treated as column 6), which is useful. Turning it on causes the command to behave in a way that is not useful, as I described.
> >
> > If you leave visual-line-mode off, then type C-p twice from "z", don't
> > you see point go to the 3rd "*" of the line "**** h4"? And if so,
> > isn't that what you meant by "the goal column actually seems to be
> > offset in some way influenced by the line prefix"? Or did I
> > misunderstand what you consider a problem in the existing behavior?
>
> Indeed, on that line, the behavior is the same with and without visual-line-mode, going to the 3rd "*".
>
> However if I go up to a list item such as "- x...........", I observe different behavior. With visual-line-mode, point ends up on the bullet, not on "x".
>
> That is surprising, no?
Not to me, it isn't, but then I've hacked on that code too much...
Anyway, the problem is the difference in behavior between
visual-line-mode on and off, and you consider the behavior with the
mode off as correct? Because this was not what your original report
said, AFAICT.
This bug report was last modified 312 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.