N
Nick Radcliffe
In the absence of an export, I've been using copy as Markdown to backup/copy notes.
There are number of oddies about this, and one flat-out bug:
Many of the notes I copied as Markdown included:
NoneBashCSSCC#GoHTMLObjective-CJavaJavaScriptJSONPerlPHPPowershellPythonRubyRustSQLTypeScriptYAMLCopy
which looks like the popup for language? (It wasn't showing, I don't think when I copied, though I suppose I can't be sure.)
The markdown is also a bit unconventional. Thing I immediately notice are:
It has a
lot* of vertical whitespace: if I replace every pair of newlines with a single one, it looks more normal.
* It's putting a lot of horizontal whitespace in too...like three spaces after bullets, for example
It's using the same bullet (
) for first level and second level items, which is legal but unusual (I think most systems use
-
for the second-level bullets
* It's using # and underline for headings. Normally it's one or the other.
I guess double newline thing might be related to why when you paste Markdown from other systems in, it loses the blank lines.
If I use either Github or Fletcher Penny's multimarkdown, quite a lot of things look wrong as a result of these issues.
Obviously, Markdown is deliberately non-prescriptive, but I think if the Markdown Typist produced were a bit more conventional, that would be good.