@publicvoit @js
Which Markdown is up for debate, but there's a few dominant dialects,many of which have features unneeded in Mastodon like tables.
Just for comparison, these are the features I'd use, except for the checkboxes it's plain Markdown:
@publicvoit @js
Which Markdown is up for debate, but there's a few dominant dialects,many of which have features unneeded in Mastodon like tables.
Just for comparison, these are the features I'd use, except for the checkboxes it's plain Markdown:
@publicvoit @js
# Test Header
This is a Test with a [link to Wikipedia](https://en.wikipedia.org).
Here's a unordered list:
- **bold**
- _italics_
- _**bold italics**_
- ~~strike~~
Numbered:
1. **bold**
2. _italics_
3. _**bold italics**_
4. ~~strike~~
Check List:
- [ ] Not checked
- [x] Checked
Inline `code` vs
block of code
@publicvoit @js Same with Orgmode (via Pandoc):
* Test Header
This is a Test with a [[https://en.wikipedia.org][link to Wikipedia]].
Here's a unordered list:
- *bold*
- /italics/
- /*bold italics*/
- +strike+
Numbered:
1. *bold*
2. /italics/
3. /*bold italics*/
4. +strike+
Check List:
- [ ] Not checked
- [X] Checked
Inline =code= vs
#+begin_example
block of code
#+end_example
@publicvoit @js For me, the backticks for inline code are more readable than the equal signs. Similar with the link, putting the text first is (IMO) more readable. But YMMV.
Orgmode probably beats out Markdown in its native Emacs PIM environment, but for pure readability I think Markdown does slightly better. Unless it's rendered, then it doesn't matter anyway.