Ihor Radchenko writes:
> 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 comman
Sam Crawford 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
> (t
On 02/07/2024 15:35, Ihor Radchenko wrote:
Sam 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 forme
Sam 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
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.
For R, there is only org-babel-R
