3 ms·
I used to agree with this, but since I started using Dropbox Paper as my primary editor, I've changed my mind. I don't need to see the markup if the editor / f
by enobrev 9y ago
I used to agree with this, but since I started using Dropbox Paper as my primary editor, I've changed my mind. I don't need to see the markup if the editor / formatting works consistently.
The different header sizes are immediately obvious without trying to find how many #'s there are. Monospace words and sections are immediately apparent without trying to figure out if i used backticks or apostrophes. And I don't want to "Preview", even if it's a live Preview. I want to see my fully formatted document as I type it without switching context.
On that note, one thing I wish _all_ markdown editors would pick up, and have only seen on StackOverflow, is the "Reference Style" links, where you can denote a link using something like [1], and then list the url below the text. I have never once, ever, needed to know and immediately see a full url while reading or editing text. Inline urls actively make editing and reviewing more difficult.
This is hidden by Dropbox Paper with an actual link as expected, but their export still has inline urls, which is standard, of course, but I don't agree with the standard.
- deleted 9y ago[deleted]
- lstamour 9y ago> ... But their export still has inline urls, which is standard, of course, but I don't agree with the standard. Just to clarify, inline urls are one of the two standard [Markdown link styles](https://daringfireball.net/projects/markdown/syntax#link https://daringfireball.net/projects/markdown/syntax#link). The other is [reference-style][ref]. [ref]: https://daringfireball.net/projects/markdown/syntax#link https://daringfireball.net/projects/markdown/syntax#link
- enobrev 9y agoThank you, I hadn't realized that was actually part of the spec. I also hadn't realized how long it had been since I actually read that document.