From 9734a6ce473c961495492151153e28635e63426d Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Tue, 10 Mar 2026 09:15:52 +0800 Subject: [PATCH] vim-patch:9.2.0130: missing range flags for the :tab command (#38216) Problem: :tab accepts a tab address range but doesn't specify this in the command specification. Solution: Add EX_RANGE and EX_ZEROR to the command specification and use ADDR_TABS (Doug Kearns). As command modifers are handled separately before these flags are tested in the ex-command parser they have no effect. However, it's better to use an accurate description and the command specification table has uses in other areas like runtime file generation for the Vim filetype. closes: vim/vim#19100 https://github.com/vim/vim/commit/49b8d9903bc7a2620ce7cf46228e16f7cd308d2e Co-authored-by: Doug Kearns --- src/nvim/ex_cmds.lua | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/nvim/ex_cmds.lua b/src/nvim/ex_cmds.lua index 08b779b7e4..93cc0f3bfe 100644 --- a/src/nvim/ex_cmds.lua +++ b/src/nvim/ex_cmds.lua @@ -2767,8 +2767,8 @@ M.cmds = { }, { command = 'tab', - flags = bit.bor(NEEDARG, EXTRA, NOTRLCOM), - addr_type = 'ADDR_NONE', + flags = bit.bor(RANGE, ZEROR, NEEDARG, EXTRA, NOTRLCOM), + addr_type = 'ADDR_TABS', func = 'ex_wrongmodifier', }, {