zc he
> Thanks for digging into this. Getting those string indices right with the LSP definitely takes attention to detail. > > I think @schrieveslaach is the expert on how we...
> where are we at on this? 1. Default UTF-16 position encoding works fine with this fix. Some clumsy conversions within ropey crate going on here, but still fast -...
> What we need is more contributors to nufmt. Agreed, but `new-nu-parser` is of higher priority IMHO.
Just checked the source code on the main branch. Only get-cursor and set-cursor are implemented. I'd like to have 2-int (start, end) version of them.
Hi @fdncred , I'd like to discuss the design choice here. Why we use a ReplState instead of just a Reedline editor in struct EngineState? Seems that the set-selection function...
@132ikl I'd like this because when the only valid options are say `foo` and `foooo`, a typical bash behavior of `f#tab` would complete the repl text to `foo` without moving...
I think it is windows specific, can't reproduce on macos.
I think your highlights.scm is the latest while the grammar is not up-to-date.
> `TSUpdate nu` says "Parsers are up-to-date!" Yes, because neovim-ts has its own copy of the parser, which is several days behind this repo.
3 solutions here: 1. remove tree-sitter-nu completely, use all files hosted by neovim-ts 2. manually specify to use the local version (which is my config for debugging) here: ```lua config...