tree-sitter-markdown VS mkdnflow.nvim

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

I like logseq for knowledge management and tasks. And since it's all plain markdown files they are easy to quickly open and search in nvim. https://github.com/jakewvincent/mkdnflow.nvim is really nice for this because it can follow the internal links and create new pages.

I've been planning to switch to https://github.com/jakewvincent/mkdnflow.nvim and re-write the function that creates diary pages, and the functions that cycle/navigate to next/prev diary pages, so that they work in subdirs... for example: main wiki is ~/diary and the main diary is in the root of that wiki and I want to be able to flexibly create dated files in any subdir without making that its own wiki so like in ~/diary/subdirxyz/2023-03-17.mkd the nextDay() function (whatever it's called) would look for next dated file only inside subdirxyz.

There are some cool features we've talked about adding to mkdnflow.nvim!!!

https://github.com/jakewvincent/mkdnflow.nvim is a similar plugin to neorg that's closer to vimwiki than to org-mode. Either way, a personal documentation system, and whatever report/scripts/grep to find things easily.

Did you see https://github.com/jakewvincent/mkdnflow.nvim/ mentioned here? I think that's the winner here (though I admit I have bias against even considering zettlekesten/zk merely due to its name: in computing we call that a wiki).

My markdown plugin mkdnflow does this (among other things). If you’re not looking for any functionality except toggling checkboxes, you could take a look at the lists module lists.lua and search for the function toggleToDo() (and those it relies on).

I'm using zk-nvim with markdown lsp, markdown / markdown_inline Treesitter and MKDNFLOW for my notes and tasks. This all works great and I also created this shortcut to archive selected lines to a different file

I use mkdnflow.nvim for taking notes in markdown. It is simple, and you can easily create and follow links.

I use markdown for all of my notes inside of Neovim and have a few custom macros and shortcuts, and heavily use iamcco's [MarkdownPreview](https://github.com/iamcco/markdown-preview.nvim) along with jakewvincent's [MkdnFlow](https://github.com/jakewvincent/mkdnflow.nvim).

Not sure what exactly you mean by editing lists and tables with ease, but my plugin https://github.com/jakewvincent/mkdnflow.nvim might check some of those boxes. What list and table editing features would be must-haves for you?