Consider removing `mini.ai`

[ro0gr]

Inspired by #1992.

It appears that mini.ai conflicts with Neovim 0.12’s incremental selection feature. Additionally, some of mini.ai’s features are now natively supported in Neovim.

For example, in

kickstart.nvim/init.lua

Lines 840 to 842 in c0cc054

	-- - va) - [V]isually select [A]round [)]paren
	-- - yinq - [Y]ank [I]nside [N]ext [Q]uote
	-- - ci' - [C]hange [I]nside [']quote

features 1 and 3 are already available in a plain nvim --clean session, at least as of Neovim 0.12 (possibly even earlier).

Of course, there are still some nice-to-have features, like "q" for quotes and "n" for next. But are these additions truly worth including as defaults in kickstart?

[oriori1703]

we can also just change the conflicting keymaps on the mini.ai side.
i.e something like this:

diff --git a/init.lua b/init.lua
index b56ce29..69176e9 100644
--- a/init.lua
+++ b/init.lua
@@ -840,7 +840,14 @@ require('lazy').setup({
       --  - va)  - [V]isually select [A]round [)]paren
       --  - yinq - [Y]ank [I]nside [N]ext [Q]uote
       --  - ci'  - [C]hange [I]nside [']quote
-      require('mini.ai').setup { n_lines = 500 }
+      require('mini.ai').setup {
+        mappings = {
          -- NOTE: Avoid conflicts with the built-in incremental selection mappings on Neovim>=0.12 (see `:help treesitter-incremental-selection`)
+          around_next = 'aa',
+          inside_next = 'ii',
+        },
+        n_lines = 500,
+      }

       -- Add/delete/replace surroundings (brackets, quotes, etc.)
       --

[ro0gr]

@oriori1703 true. To me, this is still a better option than modifying built-ins.

I suspect the comment above should be converted from yinq to yiiq 🤔 TBH, the combo feels a bit too advanced to me. Maybe I should reconsider and learn to use it.

Either way, both options(remove plugin or rename keybind) seem to be a breaking change from the user perspective.