Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Comment.nvim
:brain: :muscle: // Smart and powerful comment plugin for neovim. Supports treesitter, dot repeat, left-right/up-down motions, hooks, and more
-
nvim-ts-context-commentstring
Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
markdown-it
Markdown parser, done right. 100% CommonMark support, extensions, syntax plugins & high speed
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.
I'm sorry, I haven't gotten around to do a lot of things like better documentation. It adds markdown support to tree-sitter, which is a experimental new highlighting system. See https://github.com/nvim-treesitter/nvim-treesitter for more info.
This is simply wonderful. And unlocks a whole new world of possibility. Besides that, one thing I really love is highlighting of code fences, and guess what https://github.com/numToStr/Comment.nvim works out of the box :)
That's awesome! Does it work with nvim-ts-context-commentstring?
I've been using ikatyang/tree-sitter-markdown until now, how is this one different?
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.
Say no more (just implemented it for Catppuccin).
