Fix trailing whitespace in code literal #17939
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
MichaelHatherly
added
the
domain:docs
|
Thanks for updating my confusing entry. |
|
Would a non-breaking space work? |
Seems to work fine. Thanks. |
MichaelHatherly
force-pushed
the
mh/whitespace-literals
branch
from
1f295a5
to
d50f883
Compare
|
The |
rst apparently requires that the closing double backticks for code literals appear at the end of a "word", rather than preceded by a space as markdown allows. This means that ``` ``julia> `` ``` doesn't parse correctly. The fix is to just remove the trailing space and explicitly mention the need for a space after the `>`.
MichaelHatherly
force-pushed
the
mh/whitespace-literals
branch
from
d50f883
to
1fe9bf9
Compare
It does appear to work with GitHub's markdown parser and Julia's as well. |
|
Travis OSX error is unrelated, will merge shortly. |
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.
rst apparently requires that the closing double backticks for code literals appear at the end of a "word", rather than preceded by a space as markdown allows. This means that
julia>doesn't parse correctly. The fix is to just remove the trailing space and explicitly mention the need for a space after the>.