Fix for "\n" after backslash escape #473
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
The "\n" after backslash escape is not correctly now, so the code below is broken in HTML. a = 1 if first_flag_var and \ this_is_flag_var This commit fixes it.
|
Need not to add a test for this? |
aycabta
force-pushed
the
fix-for-nl-after-backslash
branch
from
3e36a99 to
4733565
Compare
|
OK, I added a test for this. |
|
confirmed. Thanks! |
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 "\n" after backslash escape is not correctly now, so the code below is broken in HTML.
This Pull Request fixes it.