fix(repeatable_move): repeat_last_move always uses count 1 when used in operator-pending (no) mode.

Author: Illia Shkroba

lua/nvim-treesitter-textobjects/repeatable_move.lua

@@ -43,12 +43,16 @@ M.repeat_last_move = function(opts_extend)
     return
   end
   local opts = vim.tbl_deep_extend('force', M.last_move.opts, opts_extend or {})
+  -- The call to `normal` in `force_operator_pending_visual_mode` resets `vim.v.count1` to 1 while in
+  -- operator-pending (no) mode. Meaning, that the `vim.v.count1` must be saved before the
+  -- `force_operator_pending_visual_mode` call and used later on instead of new `vim.v.count1`.
+  local count1 = vim.v.count1
   if M.last_move.func == 'f' or M.last_move.func == 't' then
     force_operator_pending_visual_mode()
-    vim.cmd([[normal! ]] .. vim.v.count1 .. (opts.forward and ';' or ','))
+    vim.cmd([[normal! ]] .. count1 .. (opts.forward and ';' or ','))
   elseif M.last_move.func == 'F' or M.last_move.func == 'T' then
     force_operator_pending_visual_mode()
-    vim.cmd([[normal! ]] .. vim.v.count1 .. (opts.forward and ',' or ';'))
+    vim.cmd([[normal! ]] .. count1 .. (opts.forward and ',' or ';'))
   else
     -- we assume other textobjects (move) already handle operator-pending mode correctly
     M.last_move.func(opts, unpack(M.last_move.additional_args))