I am very happy to see the discussion about Mark Text on Hacker News. I am the author and main maintainer of Mark Text. I will seriously think about the suggestions for Mark Text which you comment here. I also welcome everyone to submit the issue and suggestion to Mark Text on GitHub https://github.com/marktext/marktext. Thank you everyone.
I appreciate Mark Text a lot, have been switching from Typora at the beginning of the year. I'm taking all my notes with it and find features like KaTeX and Mermaid very useful. Some remarks and questions from my side:
- How is the current status the Plugin system? It would be cool to try integrating features like Pandoc Citer from VSCode or LaTeX autocompletion, but I guess that would be too much for the core.
- Since you're already using pandoc, more available export formats or the option to define own exports via settings would be useful!
- Images are linked to their current path when added. I liked Typora's feature of automatically copying them into an asset folder a lot.
Overall, great work! I might learn Vue an Electron just for the sake of MarkText. Don't listen to the Electron critics - having a reusable rendering engine and the same features as in GitLab available locally is way better than saving some RAM.
Does "more fonts" mean "any font installed on my system"? Or does it mean "a bigger hardcoded list of fonts"? If the latter, will that list include Computer Modern?
Features
Realtime preview and use snabbdom as it's render engine.
Support CommonMark Spec and GitHub Flavored Markdown Spec.
Support paragraphs and inline style shortcuts to improve your writing efficiency.
Output HTML and PDF file.
Multiple themes.
Various edit mode: Source Code mode、Typewriter mode、Focus mode.
