Current problem
The following markdown examples are not currently supported.
Proposed change
That the following markdown options to be made available:
===text===to highlight the enclosed stringText[^1]and[^1] [elaboration]for footnotesString~subscript~stringfor subscriptString^superscript^stringfor superscript> [!TEXT]for custom callouts beyondNote,Tip,Important,Warning, andCaution[text](#4b47dc)to render text with colour based on HTML colour codes
Optional Reading
In case this ends up being a place to consolidate markdown options, here are other ones I would've suggested but other posts already exist for them:Additional information
- 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)?
- Maybe escaping
12 comments
Comment by gobbe
Comment by _
Comment by vicky
Comment by _
Comment by vicky
Comment by vicky
- In single-line codeblocks (
- In multi-line codeblocks (
However, trying to escape an escape character ("\") (still in single-line codeblocks) does not work:`) it escapes normally, while,```), it doesn't:
However writing a single backslash inside backticks:\\(two "\" inside backticks renders two "\" instead of the expected one).` successfully escapes the second backtick, resulting in — as you can see — less-than-ideal results.My suggestions
- make the
- make backslashes escape normally inside multi-line codeblocks, allowing for:
to render as three backticks without the backspaces; so that copy-pasting the codeblock would work as a latex codeblock.whitespacebacktickbackslashbacktickwhitespacea special exception where in this one case the backslash doesn't escape.Comment by sodiboo
```by delimiting with````(or keep adding backticks until your codeblock doesn't contain the delimiter anymore; i use 5 in the example):``\``. i'll put it right here:\and you'll see it doesn't interact with my trailing/dangling backticks``.``requires\`\`(<-- to write that, each slash is triple and there are two backticks around the whole thing). simply putting one backslash like\``is not enough; the two backticks are still adjacent, so they still end the inline code. indeed, i agree that single-backtick inline code behaves super strangely. but using two backticks seems to prevent all that weirdness. i always use two backticks because my deadkeys make it hard to write just one backtick; as such, i've never had any problems with inline code blocks. they're generally very predictable for me.Comment by vicky
Comment by sodiboo
Comment by vicky
Comment by Spax
Comment by _