luukvbaal
luukvbaal
Porting to Nvim revealed some more differences, investigating whether those require follow-up Vim patches. `test/functional/legacy/normal_spec.lua @ 41` now fails because `scroll_to_bottom()` does not properly handle topfill at the start of...
If you see difference in behavior please provide clear reproduction steps (buffer text, window size, options, keys pressed).
Draft PR mainly intended to discuss the posed problem-solution statement. From #20416, not clearing/re-emitting "still visible" messages seems wanted. Not emitting the hit-return message also seems fair game. The handler...
> What are the downsides? From my POV there aren't any, besides changing behavior which clients may be relying on (not sure who else to ping to confirm that). I...
Are the desktop entries from the repo in its current state supposed to work? Would like to have a lightdm entry for i3 and one for i3 with gpu enabled....
Yes, both issues are also tracked here https://github.com/vim/vim/issues/14338. I'm working on a fix to restore the previous behavior, although I think it is weird/inconvenient that the various scroll keys behaved...
@monkoose I am attempting to fix any issues on top of the current patches so until proven fruitless I don't think we will revert. Sounds like a different problem indeed...
Is that our problem or up to the provider to handle?
Fine by me, updated. Not sure whether to keep the `various.txt` references. Referring to experimental API is a little weird but removing them risks forgetting them in the future.
Uhm since `range` flushes the UI in addition to marking a buffer range for redraw, and it is used in the treesitter highlighter, an (unintended but wanted?) consequence could be...