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/_lsp.lua | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'runtime/lua/vim/pack/_lsp.lua') diff --git a/runtime/lua/vim/pack/_lsp.lua b/runtime/lua/vim/pack/_lsp.lua index 7af48d529b..04949ce6eb 100644 --- a/runtime/lua/vim/pack/_lsp.lua +++ b/runtime/lua/vim/pack/_lsp.lua @@ -20,7 +20,7 @@ function methods.shutdown(_, callback) end local get_confirm_bufnr = function(uri) - return tonumber(uri:match('^nvim://pack%-confirm#(%d+)$')) + return tonumber(uri:match('^nvim%-pack://confirm#(%d+)$')) end local group_header_pattern = '^# (%S+)' -- cgit