No pairs are completed after cutting multiple lines

[maleksware]

Description

The completion works fine in standard insert mode and after cutting one line with c. When using 2c or any other motion affecting many objects, like c2w, and then typing { or ( or similar, no pairs are added, no matter the filetype and opening element of the pair.

Looks like a regression in Nvim 0.12.*. The above definitely worked before in Nvim 0.11.

Mapping bug

No response

Steps to reproduce

Use a default config and no other plugins, open a file, add a couple of lines. Enter insert mode and type {, } will also appear. Run 2c, type {, the closing brace does not appear. Escape, enter insert mode again, type {, and } appears as needed.

Minimal config

vim.cmd [[set runtimepath=$VIMRUNTIME]]
vim.cmd [[set packpath=/tmp/nvim/site]]
local package_root = '/tmp/nvim/site/pack'
local install_path = package_root .. '/packer/start/packer.nvim'
local function load_plugins()
  require('packer').startup {
    {
      'wbthomason/packer.nvim',
      {
        'windwp/nvim-autopairs',
      },
    },
    config = {
      package_root = package_root,
      compile_path = install_path .. '/plugin/packer_compiled.lua',
      display = { non_interactive = true },
    },
  }
end
_G.load_config = function()
  require('nvim-autopairs').setup()
end
if vim.fn.isdirectory(install_path) == 0 then
  print("Installing nvim-autopairs and dependencies.")
  vim.fn.system { 'git', 'clone', '--depth=1', 'https://github.com/wbthomason/packer.nvim', install_path }
end
load_plugins()
require('packer').sync()
vim.cmd [[autocmd User PackerComplete ++once echo "Ready!" | lua load_config()]]

[maleksware]

e979a8e seems to have broken this for Neovim 0.12, rolling back to ff39eca fixes the issue in 0.12.1. It's unclear how disabling on count > 0 worked previously with such motions, and why the editor upgrade changed the behaviour.

It does seem reasonable though to only disable on motions like o or O as proposed in #479 (and enable on c).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[maleksware]

Bump - not stale

[dmyTRUEk]

Can confirm the issue.

Works as intended (pairs) after: s, ch, cl, c (c space), ce, cE, C, cc
Doesnt work (doesnt pair) after:

• 1s, 2s, 3s, ...
• c1h, c2h, c3h, ...
• c1l, c2l, c3l, ...
• c1 , c2 , c3 , ... (c <n> space)
• c1e, c2e, c3e, ...
• c1E, c2E, c3E, ...
• 1ch, 2ch, 3ch, ...
• 1cl, 2cl, 3cl, ...
• 1c , 2c , 3c , ... (<n> c space)
• 1ce, 2ce, 3ce, ...
• 1cE, 2cE, 3cE, ...

So it seems to me that pairing doesnt work after entering insert mode after action with count.

My minimal config:

Details

local lazypath = vim.fn.stdpath('data') .. '/lazy/lazy.nvim'
if not (vim.uv or vim.loop).fs_stat(lazypath) then
	local out = vim.fn.system {
		'git',
		'clone',
		'--filter=blob:none',
		'https://github.com/folke/lazy.nvim.git',
		'--branch=stable', -- latest stable release
		lazypath,
	}
	if vim.v.shell_error ~= 0 then
		error('Error cloning lazy.nvim:\n' .. out)
	end
end
vim.opt.rtp:prepend(lazypath)

require('lazy').setup({
	{'windwp/nvim-autopairs',
		event = "InsertEnter",
		config = function()
			local nap = require('nvim-autopairs')
			local rule = require('nvim-autopairs.rule')
			nap.setup({})
		end
	},
})

[dmyTRUEk]

Clearing all rules and setting them manually doesnt help too:

-- in `config` function:
local nap = require('nvim-autopairs')
local rule = require('nvim-autopairs.rule')
nap.setup({})
nap.clear_rules()
nap.add_rules {
    rule('(', ')')
}

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.