Allow selection_modes logic like nvim-treesitter-objects

[rainerborene]

Contributing guidelines

• I have read CONTRIBUTING.md
• I have read CODE_OF_CONDUCT.md

Module(s)

mini.ai

Description

I'm having a hard time migrating from nvim-treesitter-objects to mini.ai with gen_spec.treesitter generator. I can't find a way to set the selection_modes without changing the mini.ai text object implementation itself.

select = {
  enable = true,
  lookahead = true,
  keymaps = {
    ["af"] = "@function.outer",
    ["if"] = "@function.inner",
    ["am"] = "@class.outer",
    ["im"] = "@class.inner",
    ["ar"] = "@block.outer",
    ["ir"] = "@block.inner",
  },
  selection_modes = {
    ["@parameter.outer"] = "v",
    ["@function.outer"] = "V",
    ["@class.outer"] = "V",
    ["@block.outer"] = "V",
  },
},

How can I set the selection mode in mini.ai in a simpler way like the above setup syntax?

[echasnovski]

Thanks for the suggestion!

No, there is currently no way to set this permanently. The suggested way is to:

• Use V explicitly for Visual mode selection.

• Force mode in Operator-pending mode. Example with the following setup:

  local ai = require('mini.ai')
  ai.setup({
    custom_textobjects = {
      F = ai.gen_spec.treesitter({ a = '@function.outer', i = '@function.inner' }),
    },
  })

  Typing dVaf will delete @function.outer match linewise instead of charwise (default).

It is possible to add opts.vis_mode to gen_spec.treesitter() to pass down to created regions. One problem here is that this will affect both captures and it will be impossible to force charwise mode (like dvif won't work to force charwise mode).

I'll think about this (as adding opts.vis_mode is relatively straightforward), but I am currently leaning to suggesting to use explicit mode forcing (as it is more versatile) or going the Vaf-d route.