fix(pack): rename confirmation buffer to again use nvim-pack:// scheme

Problem: `nvim://` scheme feels more like a generalized interface that
  may be requested externally, and it acts like CLI args (roughly).
  This is how `vscode://` works.

  Anything that behaves like an "app" or a "protocol" deserves its own
  scheme. For such Nvim-owned things they will be called `nvim-xx://`.

Solution: Use `nvim-pack://confirm#<bufnr>` template for confirmation
  buffer name instead of `nvim://pack-confirm#<bufnr>`.
This commit is contained in:
Evgeni Chasnovski
2025-11-14 12:07:03 +02:00
parent b151aa761f
commit f492f62c3d
4 changed files with 6 additions and 6 deletions

View File

@@ -283,7 +283,7 @@ mappings to a specific action by invoking `vim.lsp.buf.code_action()` with the
Example: See `runtime/lua/vim/pack/_lsp.lua` for how vim.pack defines an
in-process LSP server to provide interactive features in its
`nvim://pack-confirm` buffer.
`nvim-pack://confirm` buffer.
==============================================================================
Troubleshooting *lua-plugin-troubleshooting*