Replies: 1 comment 1 reply
|
This would be great for all sorts of uses, and the syntax presented in the markdownguide link seems about right. Save for one minor thing, that is: Fluxer prunes empty lines at the beginning and ends of messages. This would prevent the horizontal rule's use to begin or end a message, which is something I can see people wanting to do. Maybe foregoing the empty spaces as a requirement would help. With respect to the mockup though it looks borderline invisible and in practice would perhaps benefit from being brighter or thicker. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Current problem
Currently there's no real way to naturally separate markdown content without workarounds such as using custom separator emotes
Proposed change
I would like to see Fluxer support parsing horizontal rules
Additional information
Some mockups of what this could visually look like:


Acknowledgements
All reactions