monkoose
monkoose
Thanks again. I have fixed this issues and updated codeium language server to the last version.
Hello, sorry but I don't have time or motivation to maintain this plugin. Feel free to fork it and apply this patch in it. I will archive this repo now.
I have guessed that this is something with wrapped or concealed lines. But it still WRONG behavior. Why when you open it shows `1` correctly. Then you scroll once with...
To make `line('w0')` and `getwininfo().topline` to work the "logic" should detect that there are fully concealed lines before the first shown and adjust them to actually return right result. Currently...
Is there something that let the user to detect if the cursor is inside concealed region?
So you want to implement it?
I have no plans to do it myself. For me it is "quite a bit of work" with minified js with shortened variable and function names to understand codeium internals...
We could implement something like https://github.com/Exafunction/windsurf.vim/pull/447 But I'm not sure if I like it's "one neovim instance with working codeium" issue.
Seems like in general expression stops after finding first array (only for array types) ```odin package main import "core:fmt" main :: proc() { first() // [2, 2] first2() // [1,...