From f492f62c3d5fbceda60fc3a481ee1b51c60f71bb Mon Sep 17 00:00:00 2001 From: Evgeni Chasnovski Date: Fri, 14 Nov 2025 12:07:03 +0200 Subject: 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#` template for confirmation buffer name instead of `nvim://pack-confirm#`. --- runtime/lua/vim/pack.lua | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'runtime/lua/vim/pack.lua') diff --git a/runtime/lua/vim/pack.lua b/runtime/lua/vim/pack.lua index 9db73ae14e..26cffb8606 100644 --- a/runtime/lua/vim/pack.lua +++ b/runtime/lua/vim/pack.lua @@ -1057,7 +1057,7 @@ end local function show_confirm_buf(lines, on_finish) -- Show buffer in a separate tabpage local bufnr = api.nvim_create_buf(true, true) - api.nvim_buf_set_name(bufnr, 'nvim://pack-confirm#' .. bufnr) + api.nvim_buf_set_name(bufnr, 'nvim-pack://confirm#' .. bufnr) api.nvim_buf_set_lines(bufnr, 0, -1, false, lines) vim.cmd.sbuffer({ bufnr, mods = { tab = vim.fn.tabpagenr() } }) local tab_id = api.nvim_get_current_tabpage() -- cgit