vim-textobj-quote VS tree-sitter-markdown

You could write a more reliable version of https://github.com/preservim/vim-textobj-quote ?

given the existence of tree sitter grammar for markdown, I think it’d be fairly easy to implement the linter on top of it.

The original repo wasn't working since the move from ikatyang/tree-sitter-markdown to the new markdown parser by /u/deinemade/ MDeiml/tree-sitter-markdown so I kept maintaining it as a fork with the absolute basics just so I could generate the vimdoc for fzf-lua.

The new parser https://github.com/MDeiml/tree-sitter-markdown is more stable. And should be installed by default, if not just run :TSInstall markdown

I've spent the last month implementing a markdown parser for tree-sitter, and just now it was merged into nvim-treesitter. You can check it out at https://github.com/MDeiml/tree-sitter-markdown. It's not really 100% done yet, but still definitely better than the builtin markdown highlighting. To use it with neovim, update nvim-treesitter and then run :TSInstall markdown.

Looks like this scanner uses more of the parser generator features of tree-sitter: grammar.json is almost 11k lines of "definitely not easy to maintain (IMHO)" json. Where as ikatyang's version is a hand written parser. tree-sitter is not great for languages that are not deterministic. The benefits for ikatyang is that it is probably easier to maintain, the drawbacks are it can definitely crash neovim (sadly). For these types of syntax, a parser definitely needs to support look ahead and look behind, which tree-sitter does not support. This is just my not-so-computer-science-y theory.