You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Markdown rendering in Memos does not support blank line breaks within quote blocks. For example, the following Markdown:
> TEXT
>
> TEXT
results in the blank line not being included within the quote block. This behavior differs from other Markdown applications, such as Obsidian, where the blank line is properly rendered as part of the quote.
Suggestion:
I suggest updating the Markdown rendering logic in Memos to ensure that blank lines within quote blocks are properly enclosed. This change will enhance consistency with other Markdown tools and improve the overall user experience.
Thank you for your attention to this matter.
Steps to reproduce
Open the Memos application.
Create a new note.
Enter the following Markdown content like:
> TEXT
>
> TEXT
Save to render the note.
Observe that the blank line between the two lines is not included within the quote block.
The version of Memos you're using
v0.24.2
Screenshots or additional context
No response
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Issue:
Currently, the Markdown rendering in Memos does not support blank line breaks within quote blocks. For example, the following Markdown:
results in the blank line not being included within the quote block. This behavior differs from other Markdown applications, such as Obsidian, where the blank line is properly rendered as part of the quote.
Suggestion:
I suggest updating the Markdown rendering logic in Memos to ensure that blank lines within quote blocks are properly enclosed. This change will enhance consistency with other Markdown tools and improve the overall user experience.
Thank you for your attention to this matter.
Steps to reproduce
The version of Memos you're using
v0.24.2
Screenshots or additional context
No response
The text was updated successfully, but these errors were encountered: