Markdown is great... But you know what else is great? OPML. We need more tooling around OPML. It's not being used nearly as much as it should be for Personal Knowledge Management.
If it is worth keeping, save it in Markdown
111–120 of 282 posts
Re: If it is worth keeping, save it in Markdown
#112Earlier quoted context omitted.
I like Commonmark but I wish it would have been more opinionated. They chose to allow two ways to do everything[0]. Making * always be used for bold and _ always for italicizing is so much clearer, and some Markdown flavors (notably WhatsApp) do this. So you only have to do *haha* or _haha_, which also makes italic-bold more _*intuitive*_. Similarly they should have gone with one style of headings, probably with #. T…
If you want strictness, use a linter or a pretty-printer that follows your preferred style. Adopting an opinionated parser means you can't lint or pretty-print input from those with different opinions (I do not like underscores for emphasis), and thus somewhat goes against the goals of TFA here: > Markdown files are essentially plaintext with some extra syntax for common elements like sections, bullet points, and lin…
I'm surprised they didn't make a conversion tool to do MDX(old) -> AST -> MDX(new). The library support is there, but it doesn't look like anyone has created a tool to do it.
Re: If it is worth keeping, save it in Markdown
#113The killer app for markdown would be a collaborative editor that displays the raw markdown and formatted markdown side-by-side and makes both sides editable. Tech people can use `#` and `*` on one side for formatting, product people can use normal text-editor buttons like "header1", "italics", etc.
Here's a comparison chart of collaboration/teamwork plugins in Obsidian.
https://system3.md/observatory/categories/collaboration-team...
Peerdraft, Relay, and Screen Garden are all based on CRDTs, and Obsidian is also currently working on native collaboration.
(disclaimer: I work on Relay)
Re: If it is worth keeping, save it in Markdown
#114Re: If it is worth keeping, save it in Markdown
#115When it comes to web archiving, I've found that Markdown has some real limitations. Sure, it's great for basic text, but it struggles with things like embedded content and non-standard layouts. Try archiving a Twitter thread or an app-style webpage in Markdown, and you'll see what I mean. It just doesn't capture the full picture. That's why I've come to prefer formats like webarchive, mhtml, or single HTML files for…
> [Markdown] struggles with things like embedded content and non-standard layouts.
I don't share that experience. I typeset all these documents using Markdown with pandoc's div extension, transformed into XHTML, and then passed to ConTeXt:
* https://impacts.to/downloads/lowres/impacts.pdf
* https://dave.autonoma.ca/blog/2020/04/28/typesetting-markdow...
* https://pdfhost.io/v/4FeAGGasj_SepiSolar_Highlevel_Software_...
From XHTML, the document is transformed into TeX statements, which opens a world of possibilities. In the following video, custom styling is applied to nested contents:
Re: If it is worth keeping, save it in Markdown
#116Earlier quoted context omitted.
Interesting. Why not HTML? Browsers have native basic WYSIWYG editing built in, and almost every screen we look at is nowadays HTML, including the code editor. On a ` element, calling document.execCommand('bold') will make selected text bold in WYSIWYG mode. See https://jsfiddle.net/z0umpb3x/12/ for the concept. The main idea here is that I don't want to know any syntax like RTF, nor I want to use any tools.
> Why not HTML? Browsers have native basic WYSIWYG editing built in Can you point me to a page in Firefox that I can use offline to WYSIWYG edit a hypertext document without needing to use the developer console to edit raw HTML?
You can use this bookmarklet to create new pages:
data:text/html,
You can use another bookmarklet to turn existing pages or files into editable pages.
Re: If it is worth keeping, save it in Markdown
#117Earlier quoted context omitted.
> Why not HTML? Browsers have native basic WYSIWYG editing built in Can you point me to a page in Firefox that I can use offline to WYSIWYG edit a hypertext document without needing to use the developer console to edit raw HTML?
You can use this bookmarklet to create new pages: data:text/html, then save them as HTML-files. You can use another bookmarklet to turn existing pages or files into editable pages.
You can't easily take text and make it red that way, only edit the existing content.
Re: If it is worth keeping, save it in Markdown
#118well, I wish I could have saved all my old Flash sound design and game experiments to Markdown, and still be able to play them
Re: If it is worth keeping, save it in Markdown
#119100% agree. I've been using markdown for a few years after moving away from proprietary note taking apps. Although this has led to me developing my own short hand for many things in my notes. And have been looking at a way to integrate a to-do list with my notes with some Python scripts. So while my notes may rely on some personal scripts to get there most value out of them, I strongly value that they are still plain…
Maybe consider Quarto? Free and open source, integrates Python scripting directly in Markdown and/or able to call from separate scripts.
Thanks for the recommendation! Sounds interesting
Re: If it is worth keeping, save it in Markdown
#120I love markdown and use it for all my notes, however it really needs a native way to underline. I have been converting some older books and lectures to markdown and underline is used all the time. If anyone has a good solution I'm all ears.
>converting some older books and lectures...If anyone has a good solution I'm all ears.
I don't know if this helps you, but you said "older": in the 20th century world of typewriters--which had no italics--underlining was used as a substitute for italics. Transforming underlines to italics or going the other way was considered normal. You wouldn't use both in the same document.