80486DX2-66/80486DX2-66
1
0
Fork 0
Code Activity

revolt-bugs.md: sort bugs

Browse source
This commit is contained in:
Intel A80486DX2-66 2024-05-06 00:04:07 +03:00
parent d0c70a3b15
commit 59cb048e2f
Signed by: 80486DX2-66
GPG key ID: 83631EF27054609B
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
notepad/revolt-bugs.md
View file

@ -8,6 +8,7 @@
- Empty lines in code blocks have a no-break space character in them. This behavior can break some compilers/interpreters.
- If a backslash is followed by another backslash or some other symbols, it is evaluated. This breaks some kaomojis, such as shrug ¯\\\_(ツ)\_/¯.
- If a line starts with `$$`, the text of this line is not rendered, unless a KaTeX inline code is used (`$...$`).
- If a message is being edited and the user empties it and then saves it, it is deleted without a prompt.
- If you declare an unordered or ordered list, the rest of it will be treated as either (1) the same list when creating another, or (2) the content of the last item. A workaround is to use a page break (e.g. `***`) which will mark an end of a list, while it would be rendered as an empty line.
- Images of media previews are too big in relation to the text.
- In code blocks, after a sequence of one or multiple lines starting with `>`, an empty line is added.
@ -16,7 +17,6 @@
- Some markdown, such as headers without text, is evaluated. It shouldn't be evaluated.
- Using non-escaped (by a backslash) `<` followed by some text, `>`, and nothing else in a quote results in reduction of space between the visual quote block and the quote.
- When replying to messages, a single message or multiple messages being replied to are parsed as markdown, but as if all line breaks (newlines) have been removed, which creates a mix-up.
- If a message is being edited and the user empties it and then saves it, it is deleted without a prompt.
## Conclusions