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 is a tentative fix for #8. It was tested with the code block
i.e. running with a session and taking the output as evaluation results - which is a workaround for #9 as seen in #9 (comment).
Given that source block a user would see the result
whereas something like
would be expected.
ob-julia
is mainly based onob-R
. It looks as ifinferior-ess-send-input
works differently for Julia and R sessions in ESS. Specifically, inob-R
the result of evaluation is essentially one string containing the desired output. Inob-julia
the result is one string per source block line (including "\n" for each comment line). These strings get concatenated to the final result containing all those newlines. The approach taken here is to replace excessive (i.e. three) consecutive newline characters with an appropriate number of newlines (i.e. one) in the resulting output string.This does not feel like the correct fix, more like a workaround, but works without getting into different ESS session evaluation specifics. Please let me know if you can think of a better way.