tree-sitter-fish
tree-sitter-markdown
tree-sitter-fish | tree-sitter-markdown | |
---|---|---|
1 | 8 | |
27 | 358 | |
- | 3.9% | |
0.0 | 0.0 | |
about 1 year ago | about 1 month ago | |
C | C | |
The Unlicense | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tree-sitter-fish
-
TreeSitter is not parsing syntax for `fish` files.
It is though. "Fish" is listed under supported languages in treesitter. It points to this repo: https://github.com/ram02z/tree-sitter-fish
tree-sitter-markdown
-
How to pass environment variables to treesitter grammar
The markdown treesitter grammar accepts environment variables when building to tweak it's behavior. How can I pass these? Currently I am using
-
Project idea: port markdownlint to Rust
given the existence of tree sitter grammar for markdown, I think it’d be fairly easy to implement the linter on top of it.
-
New(ish) plugin: ts-vimdoc.nvim, generate vimdoc from your README.md for your plugin using tree-sitter
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.
-
Any Markdown plugin for Neovim that you recommend?
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
-
Tree-sitter for 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.
- nvim-treesitter for markdown
-
Comment.nvim <3 Treesitter and some new [chef kiss] stuff
There have been big problems with treesitter Markdown, but the good news is that a brand new version is being worked on and looks like it is going to be awesome! https://github.com/MDeiml/tree-sitter-markdown
What are some alternatives?
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
vim-pandoc-syntax - pandoc markdown syntax, to be installed alongside vim-pandoc
mkdnflow.nvim - Fluent navigation and management of markdown notebooks
marksman - Write Markdown with code assist and intelligence in the comfort of your favourite editor.
nvim - 🍨 Soothing pastel theme for (Neo)vim
vimtex - VimTeX: A modern Vim and neovim filetype plugin for LaTeX files.
vim-markdown - Markdown Vim Mode
tree-sitter-markdown - Markdown grammar for tree-sitter
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
nvim - The Ultimate NeoVim Config for Colemak Users
tree-sitter-markdown - Markdown grammar for tree-sitter