[BUG] treesitter-textobjects `settings.keymaps` 25.11 regression

[malicean]

Plugin

treesitter-textobjects

Nixpkgs Release

other

Home Manager Release

other

I have read the FAQ

• I have read the FAQ and my bug is not listed there.

Description

Hello,

Since migrating from 25.05 to the 25.11 release, treesitter-textobjects.settings.keymaps has not been taking effect. I previously used keybinds like daf to delete @function.outer, cic for change @class.inner, etc but these are no longer applying. Notably, keybinds for settings.move and settings.swap still apply. This applies for multiple languages (Rust & Nix tested).

I have provided a minimal example, but you can also run my standalone Nixvim configuration before and after regression, should you like. Both versions fall within 800-900 MiB.

• 25.05
  • nix run sourcehut:~malicean/malvim/e54632c4192576d0e6d5c02d9d2b6620e3f68aa4#lite
  • Relevant configuration
• 25.11
  • nix run sourcehut:~malicean/malvim/2f2f6c965b327929befb33e2d4ac055a5fcb483f#lite
  • Relevant configuration

Then to observe the regression with the configurations:

1. Run one configuration
2. Open a new buffer: :enew
3. Set lang to Nix: :setf nix
4. Write a simple function: x: x + 1
5. Observe the presence of cif (change inner function) and other textobject keybinds in 25.05 version, but their absence in the 25.11 version

Minimal, Reproducible Example (MRE)

plugins.treesitter-textobjects = {
  enable = true;
  settings = {
    enable = true;
    keymaps = {
      "if" = "@function.inner";
    };
  };
};

[MattSturgeon]

If it's under the "settings" namespace, that means it is something we convert to lua (as is) and provide to the plugin. The upstream plugin is responsible for implementing its settings options; perhaps a newer version of the plugin has changed how it handles keymaps?

(In contrast, options outside of the settings namespace are usually nixvim options that we implement)

Looking at https://github.com/nvim-treesitter/nvim-treesitter-textobjects, it seems the option is textobjects.select.keymaps; or in nixvim terms plugins.treesitter-textobjects.settings.select.keymaps.

This also looks like something that'll be affected by nvim-tressitter's current switch from its old "master" branch to the new "main" branch. It's worth double checking which version you have packaged currently and whether treesitter and treesitter-textobjects are in sync. cc @khaneliman

[khaneliman]

Currently both are using master branch API in nixpkgs. 'nvim-treesitter' is going to be switched to 'main' soon. 'nvim-treesitter-textobjects' is still on master branch as its default too, we might need to manually target 'main' upstream for the migration because they haven't switched their default yet.

[malicean]

Including settings.select.enable and settings.select.keymaps both fixed the issue.

I think the actionable now may be to update the documentation example for plugins.treesitter-textobjects.settings? Notice it does not use the select namespace:

{
 enable = true;
 keymaps = {
   ab = "@block.outer";
   ac = "@call.outer";
   ib = "@block.inner";
   ic = "@call.inner";
 };
 lookahead = true;
}

I think during my 25.11 migration I misread the warning for the renamed option and checked against the incorrect docs, so I wasn't getting any warnings/errors and thought my config was correct.