News for hackers. Stuff that matters.
Re:A Markdown File Should Just Open by 1dom on Thursday October 22, 2026 @04:59AM (#50192962)
Exactly, you just confirmed how complicated, complex and varied markdown rendering is, which is exactly why it should be left to markdown applications.

The OS should be able to natively open plaintext. The joy of markdown is it still largely works in plaintext.

Re:A Markdown File Should Just Open by eviks on Thursday October 22, 2026 @05:08AM (#50193031)
> The joy of markdown is it still largely works in plaintext.

Except it doesn't because it isn't, the challenges above are from editing raw. There is no joy in reading/editing anything non-primitive in MD

Re:A Markdown File Should Just Open by 1dom on Friday October 23, 2026 @08:16AM (#50207769)
Markdown was explicitly designed to be a lightweight markup language for formatting text in a plaintext editor.

You will not get any joy reading/editing non-primitive things in a markdown language not designed for reading/editing non-primitive things.

You will get joy from using the right tool for the right task.

Re:A Markdown File Should Just Open by eviks on Friday October 23, 2026 @08:53AM (#50208226)
> using the right tool for the right task.

which a plaint text editor is decidedly not since it fails at the most basic editing tasks - search and search&replace. That is the joy killer. Thus the tool described in the blog is closer to the right one for this task

Re:A Markdown File Should Just Open by 1dom on Sunday October 25, 2026 @12:44PM (#50233481)
Sorry, I can't think of a single plaintext editors, even going back to things like vi and ed, which don't support find and replace.

Markdown was designed for plaintext editors. Plaintext editors are - by the definition of markdown - a right tool for the job of markdown.

I don't have anything else to add here.