Allowed multiline CriticMarkup #9
Open
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
The CriticMarkup documentation [states](https://github.com/CriticMarkup/CriticMarkup-toolkit) that linebreaks should be avoided, but seems to permit them; also the parser seems to process them well. (In my opinion, the part on inline elements probably refers to avoiding paragraph breaks, or something causing the insertion of line breaking HTML elements.) For people who are willing to take the risk, it would be nice to highlight multiline CriticMarkup, which is what these changes do.
|
On second thought: Do you think it would be preferable to make sure it's only one |
|
The Elisp docs specifically state that "elements of I'll look into the right way of doing multi-line font lock. |
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.
The CriticMarkup documentation states that
linebreaks should be avoided, but seems to permit them; also the parser seems to process them well. (In my opinion, the part on inline elements probably refers to avoiding paragraph breaks, or something causing the insertion of line breaking HTML elements.)
For people who are willing to take the risk, it would be nice to highlight multiline CriticMarkup, which is what these changes do.