Justin M. Keyes

> For some language servers this means PUM always fills the entire horizontal width of the screen: often leaving no room to see "kind" and usually no room at all...

That would be a good starting point. I will separate those changes into a separate commit if you can't.

Note that an expected part of https://github.com/neovim/neovim/issues/30889 is that the Nvim UI protocol will annotate images. Though the Nvim TUI may be more limited (PNG only?) than what a GUI...

You can already do this via `:unmap`. And you can then opt-in by mapping things to e.g. `vim.lsp.buf.rename()`. These mappings are intentionally trivial mappings to `vim.lsp.buf.*` functions, which you can...

I think distros like lazyvim, astrovim, nvchad, or whatever, which provide inner-platforms to "disable mappings" in a different way, are totally confusing people.

https://github.com/neovim/neovim/pull/30237 added validation to `--listen`. But ctrl-c on `nvim --headless --listen ./hello.sock` does not delete the socket file. So, keeping this issue open. - Without `--headless`, the socket file is...

> if the `nvim_list_uis()` returns more than one ui, how would I know which channel to close? `:help nvim_set_client_info()`

> but I don't know how to uniquely identify the neovim client itself Nvim currently uses `stdin_tty || stdout_tty` to guess (with reasonable certainty) that a UI is the TUI:...

> `nvim_get_chan_info` says it takes a 'channel_id, or 0 for current channel'. I believe 0 is currently only applicable in the context of channel callbacks It allows any API client...

> It returned `vim.empty_dict()` for me from what context? you need to call it from a API client (which implicitly has a channel). > If it returned the channel id...