lacygoill
lacygoill
I didn't realize this would lower test coverage so much. I'll try to extract the code responsible for providing the new features in a separate script, and maybe suggest it...
> Try adding "!" to 'guioptions': > set guioptions+=! It works but it prevents us from opening links: $ vim -Nu NONE -U NONE -g +'set guioptions+=! shell=sh' +'!xdg-open http://example.com/...
> I just get the error while coding some stuff. Here is a word you might have missed on the previous line: > Steps to **reproduce** "Coding some stuff" does...
> On vim that comes with git bash, I get this issue with any uppercase letter. In insert mode, let's say I input HELLO. What's shown is: > [72;2u[69;2u[76;2u[76;2u[79;2u Try...
> It is harder to get the size of sign/linnr column because there is no dedicated function too, so it requires some hacky implementations. It doesn't invalidate the feature request,...
A long time ago, I started re-writing the legacy indent plugin for Vim9 (it's [here](https://github.com/lacygoill/config/blob/master/.vim/indent/vim.vim)). But I stopped the refactoring. At some point, I'll try to finish it, but not...
> good highlights, but too much logic and feels slow sometimes You can measure the most costly rules with [`:help :syntime`](https://vimhelp.org/syntax.txt.html#%3Asyntime). I'm not sure I could improve them much. Usually,...
> Can you provide some example how they should look. Like some correct indentation of some code structure paired with current incorrect one(based on what default vim indent file or...
> Looks OK. I had more code when I stopped working on the refactoring: vim9script # { # var d = { # } # var d = { #...