tree-sitter-markdown VS vimtex

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

The full changelog is here: https://github.com/lervag/vimtex/releases/tag/v2.14.

Feel free to open an issue on GitHub. Please take care to fill in the issue template; it's meant to help you provide useful details that make it easier for me to give a useful answer.

I use vimwiki almost daily, but it's not professional use, just daily notes and organizing my life. I started using zim but I found I really missed writing/editing with vim. Then I found vimwiki. There are things I'm not super happy about with it. I saw that /u/lervag (love his vimtex plugin) released a wiki plugin and I was/am interested in it, but I have so much in my wiki right now that I don't want to deal with conversion issues.

Definitely get vimtex and set it up so you can view the compiled document in one window, and your notes in the other. Get used to vim a bit with some vim tutorial (there are a bunch out there), and have latex shortcuts you use in all your documents.

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Obsidian is limited by its use of markdown files. You can use Overleaf, Vimtex, or LaTeX workshop on VS Code to render your tex documents.

Some language-specific plugins like vimtex also include their own text objects.

I would post an issue on the VimTeX Github page: https://github.com/lervag/vimtex/issues. That way you might also get help to disable the possible indexing. I have also needed to disable project file scanning to stop Vim from hanging, when pressing Ctrl + N to perform simple auto-complete.

Absolutely VimTeX