org babel problems with (org-babel-read "*R*")

org babel problems with (org-babel-read "*R*")

[Thomas Alexander Gerds]

after upgrading to the latest bleeding edge version I have problems
executing org-babel R blocks where the session is named *R*. the error
is this:

ELISP> (org-babel-read "*R*")
*** Eval error ***  Symbol's value as variable is void: *R*

did I miss any conventions or is this a bug?

cheers
thomas


--
Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics
University of Copenhagen, Øster Farimagsgade 5, 1014 Copenhagen, Denmark
Office: CSS-15.2.07 (Gamle Kommunehospital)
tel: 35327914 (sec: 35327901) 

Re: org babel problems with (org-babel-read "*R*")

[Charles Berry]

Thomas Alexander Gerds <tag <at> biostat.ku.dk> writes:

> 
> 
> after upgrading to the latest bleeding edge version I have problems
> executing org-babel R blocks where the session is named *R*. the error
> is this:
> 
> ELISP> (org-babel-read "*R*")
> *** Eval error ***  Symbol's value as variable is void: *R*
> 
> did I miss any conventions or is this a bug?
> 

This commit

http://orgmode.org/cgit.cgi/org-mode.git/commit
/?id=bde2348c9ecc87972d21a46a91d73ad3916650b8

broke all my :session *R* headers.

But :session "*R*" works.

C-h f org-babel-read should mention *XYZ* is treated as lisp.

Maybe (org-babel-read "\"*R*\"") works for you.

Or I suppose you could hack this with (setq *R* "*R*")

HTH,

Re: org babel problems with (org-babel-read "*R*")

[Eric Schulte]

Charles Berry <ccberry@ucsd.edu> writes:

> Thomas Alexander Gerds <tag <at> biostat.ku.dk> writes:
>
>> 
>> 
>> after upgrading to the latest bleeding edge version I have problems
>> executing org-babel R blocks where the session is named *R*. the error
>> is this:
>> 
>> ELISP> (org-babel-read "*R*")
>> *** Eval error ***  Symbol's value as variable is void: *R*
>> 
>> did I miss any conventions or is this a bug?
>> 
>
> This commit
>
> http://orgmode.org/cgit.cgi/org-mode.git/commit
> /?id=bde2348c9ecc87972d21a46a91d73ad3916650b8
>
> broke all my :session *R* headers.
>
> But :session "*R*" works.
>
> C-h f org-babel-read should mention *XYZ* is treated as lisp.
>
> Maybe (org-babel-read "\"*R*\"") works for you.
>
> Or I suppose you could hack this with (setq *R* "*R*")
>
> HTH,
>
>

I just pushed up a fix.  Sorry for the bug.

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: org babel problems with (org-babel-read "*R*")

[Thomas Alexander Gerds]

works again. thanks very much for fixing this so quickly! 


Eric Schulte <schulte.eric@gmail.com> writes:

> Charles Berry <ccberry@ucsd.edu> writes:
>
>> Thomas Alexander Gerds <tag <at> biostat.ku.dk> writes:
>>
>>> 
>>> 
>>> after upgrading to the latest bleeding edge version I have problems
>>> executing org-babel R blocks where the session is named *R*. the
>>> error is this:
>>> 
>>> ELISP> (org-babel-read "*R*") *** Eval error *** Symbol's value as
>>> variable is void: *R*
>>> 
>>> did I miss any conventions or is this a bug?
>>> 
>> This commit
>> http://orgmode.org/cgit.cgi/org-mode.git/commit
>> /?id=bde2348c9ecc87972d21a46a91d73ad3916650b8
>> broke all my :session *R* headers.
>> But :session "*R*" works.
>> C-h f org-babel-read should mention *XYZ* is treated as lisp.
>> Maybe (org-babel-read "\"*R*\"") works for you.
>> Or I suppose you could hack this with (setq *R* "*R*")
>> HTH,
>>
>>
>
> I just pushed up a fix.  Sorry for the bug.
--
Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics
University of Copenhagen, Øster Farimagsgade 5, 1014 Copenhagen, Denmark
Office: CSS-15.2.07 (Gamle Kommunehospital)
tel: 35327914 (sec: 35327901)