You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Great plugin! Love the good work dedicated to optimization.
Sometimes, when the contents of the buffer change outside the current viewport, the wrong indent guidelines are shown.
To Reproduce
Steps to reproduce the behavior:
Open any file (using src/nvim/shada.c in the video)
Scroll down to a section with indents
Make a change that creates new indents and scrolls the window
Scroll the window downward for a bit
Press u to undo your edits in step 3
Scroll back to the section that you were in during step 5, and a bit lower
Observe the wrong indent guides
Expected behavior
The correct indent guides.
Screenshots
cache_fail.mp4
Additional context
This is just an example, but the situation has occurred several times during daily use. I've patched a workaround in my local version, where any time a render isn't "lazy", it invalidates the cache for the whole buffer. I haven't noticed any performance impact by doing this, but I haven't measured anything. I'd imagine you'd want to do something more clever, though.
The text was updated successfully, but these errors were encountered:
I also frequently encounter this issue, but sorry, I've recently started an internship and found some other things that interest me, so it might be a long time before this issue gets resolved.
You can temporarily use indent_blankline as a substitute, and I will contact you once the issue is fixed.
Describe the bug
Great plugin! Love the good work dedicated to optimization.
Sometimes, when the contents of the buffer change outside the current viewport, the wrong indent guidelines are shown.
To Reproduce
Steps to reproduce the behavior:
src/nvim/shada.c
in the video)u
to undo your edits in step 3Expected behavior
The correct indent guides.
Screenshots
cache_fail.mp4
Additional context
This is just an example, but the situation has occurred several times during daily use. I've patched a workaround in my local version, where any time a render isn't "lazy", it invalidates the cache for the whole buffer. I haven't noticed any performance impact by doing this, but I haven't measured anything. I'd imagine you'd want to do something more clever, though.
The text was updated successfully, but these errors were encountered: