Sam Crawford <s...@crawf.uk> writes: >> The question is whether it is practically useful to have separate >> commands for R session and R non-session blocks. For most interpreters, >> it is not very useful - they use the same command. >> > > I agree that it's unlikely that users will want separate commands > (though tools like radian do exist). > > Regardless, there is still the issue that, if :session is not none, then > babel will ignore org-babel-R-command, as it just makes a call to > run-ess-R. So even if you don't want to add more variables (which > ultimately I'd agree with), it might still be worth wrapping that call > in something like > > (let ((inferior-ess-R-program (or org-babel-R-command > inferior-ess-R-program))) > ...)
Or we can just document that ESS defaults are used for sessions and ask users to customize inferior-ess-R-program if they need something non-standard for sessions. The problem with `inferior-ess-R-program' is that it must be executable name, and cannot be command with arguments, as in our default value of org-babel-R-command: "R --slave --no-save". In the absense of people who are actually making use of the proposed feature, I see no reasons to complicate the code. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
