From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54488@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28?
Date: Wed, 23 Mar 2022 10:04:40 +0000 [thread overview]
Message-ID: <87k0clf0hz.fsf@gmail.com> (raw)
In-Reply-To: <83pmmde484.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Mar 2022 05:29:31 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: João Távora <joaotavora@gmail.com>
>> Date: Tue, 22 Mar 2022 21:05:09 +0000
>> Cc: Dmitry Gutov <dgutov@yandex.ru>, 54488@debbugs.gnu.org
>>
>> > > 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.
>
> But you do that in a loop AFAIU, so one iteration could affect the
> next ones. But I'm just hand-waving here.
I'm not doing it a loop for destructive effect. I'm doing it for
measuring. If you're interested in the full 2018 story, it's
https://github.com/joaotavora/eglot/pull/125.
>> 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.
>
> Sorry, not going to happen.
Is it because it's a non GPL server, or just because you don't like to
install LSP servers? Other LSP servers will probably have the same
problem.
> And I don't see why that would be necessary: the problem happens
> entirely in Emacs Lisp, so the only thing we need from clangd is its
> output that Emacs uses. Can't you or someone collect that and include
> it in the recipe?
Actually, I do have that, and a LSP could be built that simply replays
those logs. But this is too complex.
I guess if you could point me to (your?) commit that changed the
behaviour in I can do the reproduction here and see the problem
myself, when I have time.
João
next prev parent reply other threads:[~2022-03-23 10:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 6:54 bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28? João Távora
2022-03-21 12:32 ` Eli Zaretskii
2022-03-21 16:37 ` João Távora
2022-03-21 17:05 ` Eli Zaretskii
2022-03-21 21:59 ` João Távora
2022-03-21 23:14 ` Dmitry Gutov
2022-03-22 9:48 ` João Távora
2022-03-22 12:16 ` Eli Zaretskii
2022-03-22 13:57 ` Eli Zaretskii
2022-03-22 14:31 ` Eli Zaretskii
2022-03-22 14:54 ` João Távora
2022-03-22 15:22 ` Eli Zaretskii
2022-03-22 16:06 ` João Távora
2022-03-22 16:53 ` Eli Zaretskii
2022-03-22 21:05 ` João Távora
2022-03-22 23:55 ` Dmitry Gutov
2022-03-23 1:11 ` João Távora
2022-03-23 3:39 ` Eli Zaretskii
2022-03-23 10:10 ` João Távora
2022-03-23 11:08 ` João Távora
2022-03-23 14:21 ` Eli Zaretskii
2022-03-24 15:01 ` João Távora
2022-03-24 15:29 ` Eli Zaretskii
2022-03-24 16:03 ` João Távora
2022-03-24 16:59 ` Eli Zaretskii
2022-03-23 3:34 ` Eli Zaretskii
2022-03-23 3:29 ` Eli Zaretskii
2022-03-23 10:04 ` João Távora [this message]
2022-03-23 13:23 ` Eli Zaretskii
2022-03-24 14:54 ` João Távora
2022-03-22 12:33 ` Dmitry Gutov
2022-03-22 13:50 ` João Távora
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=87k0clf0hz.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=54488@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
/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.