tree-sitter-markdown VS marksman

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

Although not as featureful or powerful as Obsidian I personally created a python script to help me manage the notes, and I preview them using my own blog being run locally and for the linking part I use marksman, it takes time and it might not be the best solution for everyone but it works for me.

I have never used this, but for NeoVim it looks like you might be able to use this (or hack on it a bit to make it work with LogSeq a bit better) https://github.com/artempyanykh/marksman

A hackier way that you can bend to your will and might be more vim-like is using the Marksman LSP with regular old markdown files in vim. You can go-to-definition in markdown links, etc. This is a Helix YouTuber who shows off some of the power of marksman, but all of these concepts translate 1 to 1 with neovim: https://www.youtube.com/watch?v=8GQKOLh_V5E

Have you seen https://github.com/artempyanykh/marksman which uses LSP?

I found https://github.com/jeffmm/vim-roam and https://github.com/artempyanykh/marksman . The first is a plugin where the second is an lsp and I'm sure there are more. Vim-roam codebase looks to be a couple of years old.

Interesting. Have been using https://github.com/artempyanykh/marksman up until now (in neovim, but also runs in vscode apparently).

You might want to check out https://github.com/artempyanykh/marksman. It's a Markdown LSP as well and has been out for a while. In addition to the regular markdown stuff, it also supports [[wiki-style#links]] which is particularly handy for the "personal knowledge base" types of workflows.

Perhaps you’ve tried the version before https://github.com/artempyanykh/marksman/releases/tag/2022-07-31 which fixed incremental text sync issue in neovim? If you’re still experiencing inconsistencies with a newer version, please do submit an issue to GH - the maintainer is very responsive 😉