From 7526fb449de39afb786a1a68365230996551b5c5 Mon Sep 17 00:00:00 2001 From: Sebastian Lyng Johansen Date: Thu, 10 Jul 2025 02:42:47 +0200 Subject: feat(extui): use winborder for msg window #34859 Problem: The message window is essentially a regular floating window but does not use 'winborder'. Still some "scratch" buffer options unset after it was removed from its window. Solution: Do not set the border when opening the window message. Forego passing `scratch = true` when opening a buffer, set the options manually when necessary. Co-authored-by: Luuk van Baal --- runtime/lua/vim/_extui.lua | 8 -------- 1 file changed, 8 deletions(-) (limited to 'runtime/lua/vim/_extui.lua') diff --git a/runtime/lua/vim/_extui.lua b/runtime/lua/vim/_extui.lua index 9132d1fa64..14430c5f30 100644 --- a/runtime/lua/vim/_extui.lua +++ b/runtime/lua/vim/_extui.lua @@ -87,14 +87,6 @@ function M.enable(opts) return true end) - -- Use MsgArea and hide search highlighting in the cmdline window. - -- TODO: Add new highlight group/namespaces for other windows? It is - -- not clear if MsgArea is wanted in the msg, pager and dialog windows. - api.nvim_set_hl(ext.ns, 'Normal', { link = 'MsgArea' }) - api.nvim_set_hl(ext.ns, 'Search', { link = 'MsgArea' }) - api.nvim_set_hl(ext.ns, 'CurSearch', { link = 'MsgArea' }) - api.nvim_set_hl(ext.ns, 'IncSearch', { link = 'MsgArea' }) - -- The visibility and appearance of the cmdline and message window is -- dependent on some option values. Reconfigure windows when option value -- has changed and after VimEnter when the user configured value is known. -- cgit