Add support for carriage return after admonition title #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove empty lines. Rename a test. Reformat eq op.
|
Thanks! It is indeed a bug and sorry for delaying it for so long. |
|
No worries! I think there was a misunderstanding on the initial issue, about where the two spaces occurs. Thank you :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With spaces for carriage return:
-------vvTip
Recommended VS Code extensions
Without spaces for carriage return:
Tip
Recommended VS Code extensions
GitHub renders the same.
For envs. without admonitions this allow to render like this:
Instead of this:
The first one looks more like GitHub layout, which is the ultimate goal of this PR.