GNU bug report logs - #54488
29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28?

Previous Next

Full log

View this message in rfc822 format

From: João Távora <joaotavora <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 54488 <at> debbugs.gnu.org, Dmitry Gutov <dgutov <at> yandex.ru>
Subject: bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28?
Date: Tue, 22 Mar 2022 21:05:09 +0000

[Message part 1 (text/plain, inline)]

On Tue, Mar 22, 2022 at 4:54 PM Eli Zaretskii <eliz <at> gnu.org> wrote:

>  >      do (condition-case eob-err
> >  >             (forward-char (/ (if (> diff 0) (1+ diff) (1- diff)) 2))
> >  >           (end-of-buffer (cl-return eob-err))))))
>
> I don't see how this could cause the problem you describe, but please
> note that encode-coding-region generally changes the text in the
> region, so maybe what you consider to be outside the restriction
> isn't?
>

I passed it t as the last argument, so it should be non-destructive to the
buffer.

Anyway, do you have an example of text in which this function causes
> point to return such problematic values?
>

The only example I have is the one I described already, as best as I could.
A user reported it to me, i installed clangd, and I reproduced it very
easily.

If you could consider installing clangd then running that ready-to-use
recipe, I'd venture to say it's the easiest way for you to understand the
problem.

>  Why do you have to use move-to-column instead of forward-char?
> >
> > I don't remember! Is it exactly equivalent if you're standing in the
> beginning of the line?
>
> Yes, if you have only text in the buffer (no images etc.).
>

Hmmm, it's interesting. Maybe I should just switch to that. Seems to fix
it. Until someone adds images to the source code i suppose. What's your
"etc"?

João

>

[Message part 2 (text/html, inline)]

Previous Next

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