Justin M. Keyes

~~It sounds like the `nvim_ui_attach` change plus [this](https://github.com/neovim/neovim/issues/29634#issuecomment-2355527810) will address 95% of the problem, so changing the UIEnter startup-order is lower priority.~~

> the `nvim_ui_attach` change in itself is not very useful unless it can be guaranteed to happen after the user had a chance to apply a configuration, but before any...

> Eventhough the docs on `vim.fs.normalize` mention: > > > On Windows, backslash (\) characters are converted to forward slashes (/). That does seem unexpected, and may be a bug,...

for reference, `:che lspconfig` has some logic for this https://github.com/neovim/nvim-lspconfig/blob/fb453a1a443b6ea6b54a1e4c101b1160c9d37950/lua/lspconfig/health.lua#L132-L137

Sounds like a very good idea to me. Eliminating special cases is high-leverage, like how we always use a remote UI even for the TUI. Is it expected that `mouse_spec`...

`preserve_exit` is called on deadly signal: https://github.com/neovim/neovim/blob/a2d510e1015d57f28ab20c5d2897527cae15b9c4/src/nvim/os/signal.c#L180-L181 IIUC, that only writes swap files. For SIGHUP/SIGQUIT (but not others like SIGTERM) maybe it makes sense to also write the buffer contents.

'autowrite' already (should) works like this for `:suspend` (SIGTSTP). And 'autowriteall' is intended to extend 'autowrite' behavior for "quit" (`:help autowriteall` mentions "closing the Vim window"). ## Proposal - Respect...

see - https://github.com/neovim/neovim/pull/32985#discussion_r2003451926 - https://github.com/neovim/neovim/pull/30936

needs a rebase > one single public API: `vim.lsp.inlay_hint.apply_action(action)` Seems fine if it's part of LSP. @MariaSolOs does this look like what you were expecting?

as mentioned in https://github.com/neovim/neovim/issues/30741#issuecomment-2404867582 , this is not implemented yet. > Part of the work to implement "multicursor" support will be to "atomize" input so that its structure is exposed....