Correct display of embracing operator #1675
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
Quarto supports inline code using the backtick operator [1], using backticks and curly quotes to specify the engine. Because of this, `{{ }}` is apparently parsed as inline code and renders as `{ }`. An extra level of curly braces must be added to display the embracing operator in the text.
[1]: https://quarto.org/docs/computations/inline-code.html
|
Just noting that this would solve a rather critical bug in the functions chapter, where the embracing operator is currently explained as being
|
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.
Quarto supports inline code using the backtick operator 1, using backticks and curly quotes to specify the engine. Because of this,
{{ }}is apparently parsed as inline code and renders as{ }. An extra level of curly braces must be added to display the embracing operator in the text.(I suppose this could also be considered a Quarto bug, since their parser is treating this as inline code when it clearly isn't. But this is an easy solution.)