Justin M. Keyes
Justin M. Keyes
Excellent discussion... > If you move all errors to the callback, then that prevents users from handling errors synchronously. We have `vim.wait` (+ `vim.async`) which provide a way to transform...
can you describe `capability_is_registered` and `supports_method` , how would each be presented in docs?
Using the same `supports_*` prefix definitely helps intuition (assuming the name makes sense).
Sure, technically it's a bug, but you should not be using this anyway, as the help hints.
> I'm using it to detect if I'm running in a TTY, what would be the best way to do that? In Nvim 0.11+ the TUI sets its channel info...
You can also use `vim.fn.has('gui_running')`
> I can use `term_name`. For Neovide it's `""` Neovide should fix that. All clients should set a name. Did you try `has('gui_running')` ...?
please update the title to describe the problem, not just "strange issue". is this similar to https://github.com/neovim/neovim/issues/32759 ?
The plugin is probably depending on the "stale redraw" trick. But that is only a guess. Need minimal steps, can't debug every plugin. I assume you tried with https://github.com/neovim/neovim/pull/36451 already?
> Having it visible allows it to be discovered and described in the keybindings view I think that is different than having it in the command palette.