Gregory Anders

> cc @gpanders who did this originally, the question I have is why does your `xdg-open` block? Mine also appears to not block, but I could be holding it wrong....

> And the other solution is to just disable release events. I think realistically we will (temporarily) do this before any 0.11 release anyway to give terminals time to catch...

@tomushkin See https://github.com/neovim/neovim/issues/32769

@shuhaowu Let's move discussion to a new issue so that we don't revive this old one https://github.com/ghostty-org/ghostty/issues/9631

We have `vim.ui.select` now which plugins have started using as a generic "selector UI". The current default implementation just uses `inputlist()`, so is this ticket effectively tracking a better default?...

This seems like another eventual candidate for `vim.ui.config()`: https://github.com/neovim/neovim/issues/25514 In the meantime though, supporting this variable for backwards compatibility seems fine to me. Although I am not sure that we...

I was surprised to learn today that `go_binary` does not already have a `stamp` attribute, and found this PR after trying to figure out why. Our use case is similar...

> Another thing that _might_ be worth taking into account here is potential `:restart` command ([#33953](https://github.com/neovim/neovim/pull/33953), [#32484](https://github.com/neovim/neovim/issues/32484)). I.e. it could be extra convenient if the updated session approach is available...

Love the concept of making the help system extensible. I'm not aware of any compelling argument for keeping it in C (other than maintaining Vim patches, but how often does...

> This would be great to have as built-ins. I'd be up to try a PR if there is interest in adding these as well from the core team. Sounds...