feat: allow specifying where snippet output will go#658
Merged
mfontanini merged 1 commit intomasterfrom Jun 27, 2025
Merged
Conversation
e4d3c76 to
a0693fc
Compare
Owner
Author
|
PS: this made snippet output with font size > 1 look a bit weird. I'm restructuring tests so I can catch these issues once and for all; should have something tomorrow. |
This file contains hidden or 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
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.
This adds a way of specifying where the output of an executable snippet will go, so it's not always shown right below the snippet. This can be useful in particular to place code in another column when the code itself is already long enough. To do this you need to:
+execsnippet and add a+id:<name>attribute.snippet_output: <name>. The output of the snippet will be placed here.For example:
Looks like:
The
+idproperty may have more uses in the future but for now this is all it can be used for.Closes #540
PS: this needs more testing and some better error reporting but I'm fried already.