Johannes Altmanninger

> Otherwise it would be nice if you could explicitly set completionItem.filterText = "\xi" and so on. Sorry I didn't realize that the absence of `filterText` already implies that `filterText...

yeah snippets are supported (see 22b0602f58ca2815c76ed35baef190ef6eeddc93 for how they usually work) but we don't have VSCode's extra user-defined snippets. They need to come from the language server. With rust-analyzer there...

Ideally the the language server supplies snippets, then it works for all editors. it's possible to add a new completer option that works like lsp_completions. It's probably not ergonomic because...

if we can find a way to work around this without making error messages for legit errors worse, then we can do that

does it happen with `HOME=$(mktemp -d) kak`? Without a reproducer I can't feasibly help. If the problem is really in `modeline-parse` (seems unlikely) you can use this to debug: ```diff...

> Shouldn't modeline.kak simply ignore anything but lines with kak: or vim: ? yes and it does as far as I can tell. If you can share an input file...

when I type `infoo` I get ```lua in foo)} do end ``` so it replaces some of the snippet placeholder but not all. If you see something different, you might...

`` is the recommended mapping to cycle through snippet placeholders, see the readme The completion menu is closed by typing any key. I'm not sure why `infoo` shows a different...

Interesting, I can reproduce. Running `pkill node` instead of `lsp-exit` also reproduces. It looks like the server sends an invalid (empty) URI "workspace/configuration","params":{"items":[{"scopeUri":"", even though we did send `textDocument/didOpen` earlier...

This looks like a typescript-language-server issue. Can you edit your toml config to add `--log-level=4`, reproduce the issue and report that upstream? A kak-lsp log would also contain the same...