Sam <s...@crawf.uk> writes: > I just noticed an inconsistency between the way ob-R and ob-python > select executables. For python, there are 3 variables: > org-babel-python-command, org-babel-python-command-session and > org-babel-python-command-nonsession, with the former overriding the > latter two.
This was added because it is relatively common to use different commands for session and non-session python blocks (things like ipython vs. python). > For R, there is only org-babel-R-command, which is ignored when running > as a session. > > Is it worth trying to make the R functionality as similar as possible to > the python? If so then I'm happy to submit a patch doing just > that. However, I'm not sure what is the best way to handle giving > command-line arguments to the R interpreter when initialising a session, > because you need to set inferior-ess-program to the executable > specifically, and put any arguments in inferior-R-args. 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. -- 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>
