#1001788 neovim: undoing changes results in a mix of old and new text

Package:
neovim
Source:
neovim
Description:
heavily refactored vim fork
Submitter:
Nicolas Évrard
Date:
2025-04-09 03:15:01 UTC
Severity:
important
#1001788#5
Date:
2021-12-16 09:28:18 UTC
From:
To:
Dear Maintainer,

I am sorry for this bug report because it occurs on some rare occurence and I
don't have a scenario to reproduce it. Yet it's annoying enough to deserve a
bug report. Feel free to close it as unreproduceable ;).

With the arrival of LSP I switched my configuration from ALE to the builtin LSP
for linting and so on. I made this switch some days after the release of neovim
0.5.0 ; since that time I have remarked that sometimes (I'd say 2 or 3 times a
month), when I undo my changes (not just one press of 'u' multiple presses), it
results in a mix of old and new changes.

When I don't use the LSP, I don't have the issue (but I don't know if it is
because I don't use it or because I have been lucky).

For the record I am usualy editing a python file with pylsp.
#1001788#10
Date:
2021-12-17 21:31:22 UTC
From:
To:
There were a number of fixes in the LSP stuff for 0.6.0, so can you let
me know if you see this again after upgrading to that?

Cheers,
#1001788#15
Date:
2022-03-01 16:45:35 UTC
From:
To:
* James McCoy  [2021-12-17 22:31 +0100]:

Hello,

So after a while I thought that it had indeed disappeared but I had it twice
today :(. It seems to be a problem with the virtual text and treesitter.

Here's a screenshot of the error in action.
#1001788#20
Date:
2022-07-17 02:53:01 UTC
From:
To:
If you encounter this again, can you see if running ":redraw!" fixes it?
That would help confirm whether it's just a display issue or the buffer
is actually in a bad state.

Cheers,
#1001788#25
Date:
2024-03-23 14:27:53 UTC
From:
To:
Is this something you're still running into?

Cheers,
#1001788#30
Date:
2025-04-09 03:13:13 UTC
From:
To:
Shall this be closed? The bug was originally reported for v0.5 and we
are now on v0.11