Improve markdown support. #817
Merged
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
thawk
force-pushed
the
markdown_trim_indentation
branch
2 times, most recently
from
6e0b372
to
fcc340e
Compare
thawk
force-pushed
the
markdown_trim_indentation
branch
from
2d24e9c
to
573e459
Compare
|
Hmm... May I ask you to submit a separate PR for each feature / issue. In particular, I'm not convinced about #816 but would be happy to merge the others. |
1. Support `marked`, you can using it instead. impress#811 2. Auto trim the indentation, so it can be indent like regular HTML. impress#812
thawk
force-pushed
the
markdown_trim_indentation
branch
from
573e459
to
cd5ce77
Compare
|
Thanks. As far as I can see, this is ready to go as is! Nice work. |
Closed
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.
marked, you can using it instead. Upgrade Markdown parser #811Trim common leading indention for Markdown #812