markup VS marktext

Btw github supports more than just markdown: https://github.com/github/markup#markups

I'm not sure 4. works for colors/styling, style attributes are stripped: https://github.com/github/markup/issues/119

I found this issue, which does not show much traction: https://github.com/github/markup/issues/994

For sharing settings and lore with players, GitHub wiki. Understands Org and several other formats thanks to GitHub Markup, so I can copy in (and trim down) my original notes without much fuss.

Re: https://github.com/github/markup/issues/533

I’m the main author of KeenWrite (see screenshots), a type of desktop Markdown editor that supports diagrams. It’s encouraging to see that Mermaid diagrams are being supported in GitHub. There are a few drawbacks on the syntax and implications of using MermaidJS.

First, only browser-based SVG renderers can correctly parse Mermaid diagrams. I’ve tested Apache Batik, svgSalamander, resvg, rsvg-convert, svglib, CairoSVG, ConTeXt, and QtSVG. See issue 2485. This implies that typesetting Mermaid diagrams is not currently possible. In effect, by including Mermaid diagrams, many documents will be restricted to web-based output, excluding the possibility of producing PDF documents based on GitHub markdown documents (for the foreseeable future).

Second, there are numerous text-to-diagram facilities available beyond Mermaid. The server at https://kroki.io/ supports Mermaid, PlantUML, Graphviz, byte fields, and many more. While including MermaidJS is a great step forward, supporting Kroki diagrams would allow a much greater variety. (Most diagrams produced in MermaidJS can also be crafted in Graphviz, albeit with less terse syntax.)

Third, see the CommonMark discussion thread referring to a syntax for diagrams. It’s unfortunate that a standard “namespace” concept was not proposed.

Fourth, KeenWrite integrates Kroki. To do so, it uses a variation on the syntax:

    ``` diagram-mermaid

I thought it only rendered files in the repo (match by extension). Does GH also allow asciidoc(tor) syntax in comments and issues?

* Note: Sadly, include is not supported on GH. https://github.com/github/markup/issues/1095

Marktext editor:

Marktext - A Markdown file editor. How to write in Markdown

Well, see comments below but you're wrong. I now huse Marktext and it's simply perfect.

I tried MarkText, but the collapsibility seemed terribly buggy, and a brief internet search did not increase hope.

I normally take Markdown notes with quick sketches from time to time with a Wacom tablet. I've used Xournal++ and Marktext to do all this, exporting my sketches into image files and inserting them into Marktext. However, I am starting to feel fatigued with this workflow and I discovered that Obsidian and the Excalidraw plugin could be an all-in-one solution for what I do, instead of having to work between two apps and exporting my sketches manually.

I have used syncthing + marktext[0] and or ghostwriter[1] depending on the content of my notes. For a daily journal I like to use ghostwriter as it has almost no distraction and it forces me to focus. It just got shifted over to being maintained by the KDE team and I really enjoy it.

I liked marktext over joplin for similar reasons. But I am probably a little overzealous in my search for distraction free note taking. I assume joplin provides more feature sets, I just happened to want less features for what I do on a day to day.

[0]https://github.com/marktext/marktext

I know I am a little late, but I have had great experience with MarkText (FOSS, a bit buggy, but the best at what it does by far), Ghostwriter (FOSS, a good editor, recently absorbed by KDE), Visual Studio Code/VSCodium with [Markdown Editor](andhttps://marketplace.visualstudio.com/items?itemName=zaaack.markdown-editor) (a WYSISWG markdown editing extention) and Obsidian (which I think you already have heard of).

Written using marktext