tree-sitter-markdown VS Comment.nvim

I've been using ikatyang/tree-sitter-markdown until now, how is this one different?

parser_configs.markdown = { install_info = { url = "https://github.com/ikatyang/tree-sitter-markdown", files = { "src/parser.c", "src/scanner.cc" }, }, filetype = "markdown", }

I am assuming that such context information might be available through the treesitter interface (https://ikatyang.github.io/tree-sitter-markdown/). I would appreciate any pointers that you may have on how I might be able to leverage this interface to get context-dependent snippets.

I wanted to make you aware of this commit: https://github.com/ikatyang/tree-sitter-markdown/commit/4d77c426ed177859324f4a82552f6039a05df818

Treesitter is a syntax parser that'll build a tree-like structure to enable anything from excellent syntax highlighting through to complex refactoring. There are so many creative ways you can use Treesitter, from jumping around text objects to commenting sections of code, it's a must-have in my books.

A couple nice quality of life plugins would be: Comment (which lets you use a keybinding to comment/uncomment things), Autopairs (which will make the paired brackets/parentheses/etc.), and Rainbow2 (which color-matches the pairs if things like parentheses).

I am reading the documentation for the [Comments](https://github.com/numToStr/Comment.nvim] plugin with :h comment.config and I see this

I was wondering what plugins you use for comments, actually, I'm using numToStr/Comment.

Nowadays, people (mostly) autogenerate their help docs with either markdown or emmmylua are their source. You are facing an issue that I faced before with Comment.nvim.

Comment.nvim?

Based on your reply I recommend taking out the comment plugin, replacing it with https://github.com/nvim-treesitter/nvim-treesitter-textobjects and https://github.com/numToStr/Comment.nvim