From: Thomas Alexander Gerds <tag@biostat.ku.dk>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Charles Berry <ccberry@ucsd.edu>
Subject: Re: org babel problems with (org-babel-read "*R*")
Date: Wed, 10 Apr 2013 19:07:04 +0200 [thread overview]
Message-ID: <86sj2y8gcn.fsf@biostat.ku.dk> (raw)
In-Reply-To: <87r4ijiruo.fsf@gmail.com> (Eric Schulte's message of "Tue, 09 Apr 2013 10:36:15 -0600")
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)
prev parent reply other threads:[~2013-04-10 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:35 org babel problems with (org-babel-read "*R*") Thomas Alexander Gerds
2013-04-09 16:21 ` Charles Berry
2013-04-09 16:36 ` Eric Schulte
2013-04-10 17:07 ` Thomas Alexander Gerds [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sj2y8gcn.fsf@biostat.ku.dk \
--to=tag@biostat.ku.dk \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).