More Syntax Preference switches

[Crissov]

Currently Typora lets its user decide whether they want

• Strict Mode (GFM/CM compatibility)
• Heading Style:
  • ATX #
  • ATX with suffix # … #
  • Setext ===
  • variable-width Setext =====
• Unordered List:
  • -
  • +
  • *
  • possibly depending on nesting level
• Ordered List:
  • 1. … 2. … 3. …
  • 1. … 1. … 1. …

Gruber Markdown, Commonmark, GFM and other extensions (which I will ignore) offer some additional alternative syntax choices that you might want to expose to the user:

• [ ] Ordered List:
  • 1) … 2) … 3) …
  • 1) … 1) … 1) …
  • a) … b) … c) … #755 not in MD, CM, GFM
• [ ] List default:
  • strict
  • loose (every list item surrounded by blank lines)
  • loose parent (nested list items are strict, their parents are loose)
• [ ] Thematic Break:
  • ----
  • ****
  • ____
• [ ] Emphasis:
  • *em* **strong**
  • _em_ __strong__
  • *em* __strong__
  • _em_ **strong**
• [ ] Code Block:
  • ␠␠␠␠ (indented)
  • ~~~ (fenced)
  • ``` (fenced)
• [ ] Plain Link:
  • automatic http://example.com and [email protected] not supported by CM but in GFM
  • short <example.com> and <[email protected]> not supported by CM
  • standard <http://example.com> and <[email protected]>
  • verbose <http://example.com> and <mailto:[email protected]> not required by CM
  • inline [example.com](http://example.com) and [[email protected]](mailto:[email protected])
  • reference [example.com][example.com] and [[email protected]][[email protected]]
  • collapsed [example.com][] and [[email protected]][]
  • shortcut [example.com] and [[email protected]] #744
• [ ] Link Title:
  • [text](target "title") and [label]: target "title"
  • [text](target 'title') and [label]: target 'title'
  • [text](target (title)) and [label]: target (title) least compatible
• [ ] Link Target:
  • [text](target) and [label]: target
  • [text](<target>) and [label]: <target>
• [ ] Space in URL:
  • <long target> CM, MD?
  • long%20target MD, CM
  • long target HTML
  • long target HTML
  • long\ target
  • long target
• [ ] Forced Line Break: interacts with Whitespace / Line Break
  • ␠␠␤ (2 spaces) classic MD
  • \␤ (backslash) CM
  • ~~␤ (just new line) not CM but GFM~~
• [ ] Position of Reference Link Definition: #985
  • directly after block of first use
  • directly after block of last use
  • before heading following first use
  • before heading following last use
  • end of document

There should also be a single control for the (minimum, maximum or fixed) number of repeated characters in Setext heading underlines (1+, = or -), thematic breaks (3+, *, - or _) and code fences (3+, ~ or `).

[vassudanagunta]

@Crissov Can you covert the list above to a task list? That way it's easy to see which items have been addressed and which not. GitHub has special support for them.

You may or may not want to merge the two halves of the list, as you can use checked boxes to identify those items "currently supported".

[vassudanagunta]

Also, you may want to generalize the "Forced Line Break" item. See #4759.

[ben-zen]

Has there been any progress on any of these options? I'm personally looking to specify _em_, **strong** as my syntax, since I've been using that across other editors, and I like consistency across my files.

[kbd]

It kills me that there are multiple ways to specify italics but no way to specify underline without resorting to HTML tags. It would be great if there was an option to render _underline_ as underline instead of emphasis.