Yi Ming

Yes, that might be a joke that isn't funny, queries could not be synced between two branches after that. But if we are certain about making this change, we could...

@clason Could you please take a look at e83e3ebed7c82d01ab97f612d3cab2c26e5032bf? Previously, we were using `#make-range!`, so the corresponding range didn’t have a capture, I think this is why we used `iter_matches`....

Oh, I realized there is indeed an issue with this change regarding quantified captures. My previous manual tests were too simple, sorry about that. Quantified captures don’t combine multiple nodes...

Should be done now. I think there's only `vim.treesitter.language.get_lang` does not exist in 0.7.

Update: I have temporarily frozen this PR because I realized that upstream is still making changes to the API.

It should be, or it may not be changed that frequently.

Now the `server_configuration.md` is generated, not manually edited.

@glepnir Could you please review it?

> best approach is to popup a notify and keep it available and remove it in the next release. It does, you can see in [there](https://github.com/ofseed/nvim-lspconfig/blob/7345e004eaf0bda621df39322c5fa32aaf53e975/lua/lspconfig.lua#L30-L33), the snippet redirects `tsserver`...

@polyzen Not that related. There are two points I want to emphasize. 1. Changing the name will not break users' configurations, `lspconfig.tsserver.setup{}` is still valid and will only have a...