Disable move mapping for specific language

[Jendker]

Hello,
Is there a way to disable move mapping for a specific language, i.e. enable it only conditionally? I would like to disable the function move keymaps (]m etc.) for cpp.

[kiyoon]

You'll need to manually map those keymaps. You can use :TSTextobjectGotoNextStart @function.outer

[Jendker]

Great, that helps! Anyway, do you know why @function.outer is set on lines where template variables are defined? E.g. it would stop on:

  Eigen::Transform<double,3,Eigen::Isometry> test(Eigen::Isometry3d::Identity());

Isn't that a bug?

[kiyoon]

I haven't used C++ for a long time, and it's better if someone with more experience contributes to writing queries. If you're interested, it's not too difficult. You need to install nvim-treesitter/playground and open it with :TSPlaygroundToggle. Press o and it will open a buffer to put queries in. Paste the queries from this repo queries/cpp/textobjects.scm. Then you'll see which parts of your code are highlighted with the queries. You can tune the wrong queries (or write new queries if you want) and create a PR.

If you're not interested, you can also make an issue and describe in more detail what the problem is. Someone else may help fixing the issues.

[Jendker]

Wow, that's very useful. I'll play with it and create the PR after I leave the playground ;) Thank you for the patience and help!

[kiyoon]

No worries, any contribution will be much appreciated!

[Jendker]

I couldn't fix it by myself - I am not proficient with lisp queries. I have opened an issue here: nvim-treesitter/nvim-treesitter#4552 I still learned something about it, so thank you a lot! Hope opening the issue still helps :)

[kiyoon]

I initially thought it could be the query bug, but reading through the issue it looks like a parser bug as mentioned in the comment. If the parser says that's function declaration when it's clearly not, there's nothing much we can do with queries. Anyways thanks for discovering the issue!