From 4b643d7068e871e4bee8ab74f3f0a054c242fa33 Mon Sep 17 00:00:00 2001 From: Shadman Date: Fri, 27 Mar 2026 16:24:14 +0600 Subject: feat(progress): set Progress-event pattern to "source" #38495 Problem: Currently, there's no way to distinguish progress messages coming from different sources. Nor can Progress event be easily filtered based on source. Solution: - Add "source" field to nvim_echo-opts. - The Progress event pattern is now defined by the "source" field. - Include the "title" as ev.data. - Unrelated change: set force=false to disable nesting. --- runtime/lua/vim/_meta/api.lua | 1 + 1 file changed, 1 insertion(+) (limited to 'runtime/lua/vim/_meta/api.lua') diff --git a/runtime/lua/vim/_meta/api.lua b/runtime/lua/vim/_meta/api.lua index 380058a287..65d05dac1e 100644 --- a/runtime/lua/vim/_meta/api.lua +++ b/runtime/lua/vim/_meta/api.lua @@ -1139,6 +1139,7 @@ function vim.api.nvim_del_var(name) end --- - kind (`string?`) Decides the `ui-messages` kind in the emitted message. Set "progress" --- to emit a `progress-message`. --- - percent (`integer?`) `progress-message` percentage. +--- - source (`string?`) `progress-message` source. --- - status (`string?`) `progress-message` status: --- - "success": Process completed successfully. --- - "running": Process is ongoing. -- cgit