nvim VS tree-sitter-markdown

I read the installation documentation and the problem is that it is very general. https://github.com/catppuccin/nvim

catppuccin

I prefer https://github.com/catppuccin/nvim

i have been able to install catpuccin theme (this one https://github.com/catppuccin/nvim) but i do not know how to put colorscheme catppuccin-latte in the config file on lunar vim. can anyone help me boys

I have consulted the catpuccin website and the github and followed their instructions but I feel like I'm missing something as I neovim still can't find the theme.

Im using lazy.nvim to load my colorscheme as plugin. This works as intended as long as i load the standard version of the colorscheme. In my example its catppuccin which translates to catppuccin-mocha. I cant get it to work with a variant of the colorscheme, for example catppuccin-latte. This is how my current plugins/colorscheme.lua:

I like Catppuccin (I use it for everything I can) personally

For anyone who needs this and uses catppuccin colorscheme, that's how I did it in init.lua (note: you have to put this before applying the colorscheme):

The markdown treesitter grammar accepts environment variables when building to tweak it's behavior. How can I pass these? Currently I am using

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

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.

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