bfredl
bfredl
@SleepySwords great work! Not everything needs to work in a MVP PR. We should start with completely disallowing inline virtual text in ephemeral marks (and then consider limited functionality as...
Merged, thanks @SleepySwords , @tom-anders and everyone else who have contributed with code and testing! As always with a master feature, API and feature details is subject to change until...
same root issue as #10070 ?
@taylan97 you are right, it is not exactly the same issue. But ideally we can refactor the code directly to fix both issues at once.
This should be ready for testing. The user visible changes should be as described in news.txt > Extmarks now fully supports multi-line ranges, and a single extmark can be used...
@lewis6991 I implemented all the `pending` tests for ranged signs. Note in one case I had to change the ordering of the the signs, does that look fine to you?
I think the option is not implemented. but it could be made into a (pure) ui_option, like 'linespace'.
Wouldn't `win_execute` (in vim docs but not yet implemented) solve the problem? Or I guess it could be called `nvim_win_command` in nvim API.
I did a bit of testing. The issue seems to be with when a buffer is added to the buffer list and not loaded. When `nvim_win_set_buf` is called on such...
> "zero side effects" doesn't seem to be the right goal. It should have all the effects that follow the autocmd based lifecycle that vim normally uses. You didn't enter...