mini.ai: use different search_method for treesitter textobjects?

[Bvngee]

I apologize if this question has already been answered or explained elsewhere that I could not find.

In most cases, I think search_method = 'cover_or_next' is the best. However, when working with ai.gen_spec.treesitter() textobjects, I find that the "or_next" part gets annoying; that is, I want these specific textobjects to only match when my cursor is within their bounds (which I believe search_method = 'cover' does), for example to prevent jumping 30 line down when I do a cif. Is there a way of specifying search_method for different textobjects? (I don't see anything obvious here...)

PS. I absolutely love what you're doing with mini.nvim, thanks for the awesome work <3

[echasnovski]

I don't think this was answered before, so no need to apologize :)

Although not straightforward, there is a way to do this. The gen_spec.treesitter() function returns a callable (i.e. function) specification. This returned function has the same signature as find_textobject(), which in turn can be configured to use specific search method via opts.search_method.

So the solution here would be to wrap the output of gen_spec.treesitter() in own function which forces specific search method. Here is an example for "function definition" textobject:

local ai = require('mini.ai')
local spec_ts = ai.gen_spec.treesitter({ a = '@function.outer', i = '@function.inner' })
local spec_ts_cover = function(ai_type, id, opts)
  opts.search_method = 'cover'
  return spec_ts(ai_type, id, opts)
end
ai.setup({
  custom_textobjects = {
    F = spec_ts_cover,
  },
})

---

That said, my recommendation would be to use 'cover' method as the main one and explicitly use an / al / in / il variants if you want next/previous textobject.

[Bvngee]

I kinda thought it would be something like that :) thanks so much!