Stephan Seitz

We have a implementation of local highlighting (just use is-local?) But it is not used because our current implementation is to slow (mainly wrong data structures and single buffer pass)....

Why should copying our implementation be a problem for GNU MELPA? Isn't the actual problem for you the implementation in Lua? Our implementation could be improved regarding speed (better caching...

@leungbk we know all the contributers and could ask them about dual licensing if this is an issue.

I think auto_expand doesn't make sense as a global option. It would also select `parameters` line-wise. Would be better as a per-textobject option.

So none of the combinations `daf` (delete a function) `vaf` (select a function) would work for? Not even the go-to commands?

@artemrakov Even, `:TSTextobjectSelect @function.outer` wouldn't work for you?

I guess this either requires: https://github.com/nvim-treesitter/nvim-treesitter/pull/493 or we just have a assignment textobject whose "inner" is either rhs or lhs. For python: ``` (assignment left: (_) @lhs.inner right: (_) @rhs.inner)...

The description is inaccurate in a way that we only set the bindings dynamically when tree-sitter is enabled for the buffer. The which-key hints will however appear for all buffers....

Ohh! `nvim_buf_set_keymap` already has a `desc` key!