numToStr

One thing to note is that some language has different name for comment node. Like in Rust you have `line_comment` and `block_comment` unlike Lua/C where you only have `comment` node.

The doc says `@spell` capture is used from `spell.scm` but `@comment` capture is used from `highlights.scm`. This might confuse some people, and also makes me wonder what if I want...

If anyone finds this destructive, then they can stick with https://github.com/numToStr/Comment.nvim/releases/tag/v0.6.1

Thanks @rafamadriz for putting this together. Just one thing, isn't it better to start the description with `Toggle comment ...` for toggle mappings. Thoughts?

@rafamadriz I agree with you. Please review the requested changes then we could go ahead with merging this :)

For testing sample.tsx ```tsx const Yoo = () => { return ( hello { return ( IDK ); }, }} > hello {true ? "true" : "false"} {true && "true"}...

It seems this is blocked by the following upstream issues: - https://github.com/neovim/neovim/pull/15330 - To capture sibling comment or attribute nodes using the `+` quantifier - https://github.com/neovim/neovim/pull/17099 - To easily iterating...

@kuntau It would be helpful if you can test this out and report any cases where comments are not correct apart from the issues that are already listed :)

Previously mentioned issues are now fixed (workaround) so this is now usable (I am using it) but there might be some cases where different commentstring might get used. I am...

> I was trying this out, it seems that this doesn't trigger for `.tsx` files? Works for me though. Do you have tsx parser installed? > though it seems that...