Justin M. Keyes

> Expected behavior: composition order is exposed in the UI protocol. What would this look like? An extra property in a UI event (which one)? ~~In `:help ui-events` I don't...

> another numerical property after `zindex` would be ideal. And it should be the same as the `comp_index` Is it actually ideal, or would it make sense to adjust the...

> Yes, currently we need both. Z-index to group shadows and blur. And the composition order to decide which window, or part of it, should actually be rendered within the...

Does this depend on the unreleased `nvim__complete_set` api? Can you try removing parts of the `showDocumentation` handler to narrow down which parts are essential to reproduce the issue. Is it...

Definitely. The manual steps are listed here (but there's likely a much better way, I just didn't search for it...): https://github.com/neovim/node-client?tab=readme-ov-file#regenerate-documentation-website

> If it should go somewhere else, please tell me where to put it. Also, setting keymaps for only the `prompt` buffer type feels very hacky in the way I've...

I've not seen E828. What system do you see this on? quoting https://github.com/pixelastic/vim-undodir-tree : > The main goal of this plugin is to avoid the E828 error one can get...

> I just thought that this seems exactly like the kind of thing NeoVim would change over Vim Nothing's blocking it, but it still needs a human to think about...

Same answer as before: https://github.com/neovim/neovim/issues/7073#issuecomment-328358428

> the vimscript bridge overhead can be expensive. It's worth considering adding a Lua version of this function and marking this as legacy. Those cases have Lua's stdlib and vim.uv...