I like this more than you’d think; my whole website is an extended exercise of Doing Cool Stuff with CSS and HTML generated from Markdown, but I always feel a little uncomfortable doing anything too fun when userstyles are not common practice. I could totally create a style switcher with Javascript, but… wouldn’t it be better if that were built into the client?
Reader mode in Firefox is what I’d like to fall back to, but it doesn’t handle my footnotes right now. :(
this one drives me nuts. I read an issue on this and the markdown people were insistent on letting text flow through newlines
FYI you can force newline with backslash like
Once upon a time\ there was a underwhelming text formatting standardHowever it’s not always supported.
For example
lemmy supports it (you can check comment’s source)
Github however, does not.
thanks, true. my peeve is with disregarding normal newlines. from a utilitarian point of view it probably makes sense, just a personal pet peeve.
I think it makes sense if you’re imagining a workflow where something is going from terminal type display, where line width is to be enforced with rigor and no mercy, to a display format, where it’s really the CSS’s problem. That said, it has killed my old habits about distinguishing soft and hard breaks, so …
yep, as long as a main target is an html display, it makes sense. in my case, I take notes in a way that restrains my syllable count to about 10-15 per line to encourage conciseness and my target is pdf—not a use case I expect markdown to accomodate, but it would be nice if I could tell pandoc to preserve new line but pandoc defers to md rules
Not sure what you mean by that. Terminals do soft-wrapping and any human formatting should rely on soft-wrapping rather than hard-coding paragraph formatting.
Not a rationale my team would accept re: git commit msg line length :)
No, I definitely agree with you. Markdown is a human format so readability newlines should be soft-wrapped rather than hardcoded. It should respect newline as it was intended.