Justin M. Keyes
Justin M. Keyes
> The most important "feature" of `on_new_config` is that it is running in a Lua coroutine. Should we change any of the existing callbacks to be coroutines? Why do we...
> downside of this is that we'd never be able to save resolved configs as they are dynamic Yeah, also removes opportunity for serialization, auto-generated UIs, and makes troubleshooting harder....
With https://github.com/neovim/neovim/pull/34550, if `cmd` is defined as a function it now receives the resolved `config` as the 2nd arg.
Try Nvim 0.11, or the latest development version. The [Releases](https://github.com/neovim/neovim/releases/tag/nightly) page has pre-built archives for Linux/Windows/macOS. Check `:version` to confirm the version.
@ntrrgc Is that plugin writing to stdout? That would break the channel. We do need to provide better feedback for that situation. On the `nvim` side, we should drop invalid...
see https://github.com/neovim/neovim/issues/6414#issuecomment-290928946 for a possible solution
Flicker caused by non-trivial functions, especially RPC/API (though this case is not RPC), is kind of a general, known topic, but I couldn't find tracking issue.
Possibly could be handled by single-file mode. The larger topic of remote handling is tracked in https://github.com/neovim/neovim/issues/21635
Feel free to reopen targeting `lsp/*`. Not accepting changes to `lua/lspconfig/configs/*`