Proposed change- `String^superscript^string` for [superscript](https://www.markdownguide.org/extended-syntax/#superscript)- `> [!TEXT]` for custom callouts beyond `Note`, `Tip`, `Important`, `Warning`, and `Caution`Added: +- `[text](#4b47dc)` to render text with colour based on HTML colour codes# Optional Reading
Show
Additional markdown syntax
Current problem
The following markdown examples are not currently supported.
Proposed change
That the following markdown options to be made available:
I believe highlight defaults to yellow, but would probably not be noticeable on light themes, so perhaps a custom colour option?
Not sure how to implement custom iconography for custom callouts, maybe reference an inline SVG?
Footnotes would behave the same as clicking a reply header
There was a request for nested code blocks that show the code block inside with fully visible syntax, but I don't know what the syntax for that should be
Maybe escaping ` with \ (currently it renders \ directly)?
Edited by _
Changes
Additional information- Not sure how to implement custom iconography for custom callouts, maybe reference an inline SVG?- Footnotes would behave the same as clicking a reply headerAdded: +- There was a request for nested code blocks that show the code block inside with fully visible syntax, but I don't know what the syntax for that should beAdded: + - Maybe escaping `\`` with \ (currently it renders \ directly)?
Show
Additional markdown syntax
Current problem
The following markdown examples are not currently supported.
Proposed change
That the following markdown options to be made available:
I believe highlight defaults to yellow, but would probably not be noticeable on light themes, so perhaps a custom colour option?
Not sure how to implement custom iconography for custom callouts, maybe reference an inline SVG?
Footnotes would behave the same as clicking a reply header
There was a request for nested code blocks that show the code block inside with fully visible syntax, but I don't know what the syntax for that should be
Maybe escaping ` with \ (currently it renders \ directly)?
Edited by _
Changes
Proposed change- `Text[^1]` and `[^1] [elaboration]` for [footnotes](https://www.markdownguide.org/extended-syntax/#footnotes)- `String~subscript~string` for [subscript](https://www.markdownguide.org/extended-syntax/#subscript)Removed: -- `String~superscript~string` for [superscript](https://www.markdownguide.org/extended-syntax/#superscript)Added: +- `String^superscript^string` for [superscript](https://www.markdownguide.org/extended-syntax/#superscript)- `> [!TEXT]` for custom callouts beyond `Note`, `Tip`, `Important`, `Warning`, and `Caution`
Show
Additional markdown syntax
Current problem
The following markdown examples are not currently supported.
Proposed change
That the following markdown options to be made available: