Yi Ming

The information will also be shown in the default quickfix window 

I agree that overriding the handler is a good idea because it only takes dozens of lines of code to implement this feature through overriding (in fact I thought of...

btw, I also disagree with officially providing inlay hints at the end of the line and then providing them through configuration, because the implementation is too subjective. For example, what...

It's supported in luasnip, see https://github.com/L3MON4D3/LuaSnip/blob/master/DOC.md#standalone. While luasnip did not support automatically loading it, writing an autocmd of `DirChange` to load it is not that hard. The most important feature...

@clason we could continue our discussion in https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/672#issuecomment-2300006562 here.

Some textobjects need the `make-range` directive to be defined, and then we read them in `metadata`, so it's impossible to convert these `Range` into `TSNode`. Luckily there is already https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/612...

> but is this a fully safe change? This is what I am concerned about most too. I think we can handle the problem with `#offset!`. `#offset!` tries to change...

> The difference here is that the original code uses the "metadata" ranges as primary objects, Honestly, it is a rather complicated situation. It uses ranges from `TSNode` primarily, and...

Brief summary, three sources of range: * From `TSNode:range()` * From `metadata[capture_id].range`, which is created by `#offset!`, could be treated as modified `TSNode:range()` * From `#make-range!`, no relevant `TSNode` object....

Since the `main `branch has already broken user configurations, it wouldn't be a particularly big issue if it continues to break user queries, lol. However, one point I want to...