From: Bernd Weiss <bernd.weiss@uni-koeln.de>
To: Dan Davison <dandavison7@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel][R] buffer-wide and code block specific use of :session
Date: Sat, 12 Feb 2011 15:42:44 -0500 [thread overview]
Message-ID: <4D56F0C4.1020500@uni-koeln.de> (raw)
In-Reply-To: <m1ipwpt89p.fsf@94.197.159.103.threembb.co.uk>
Am 12.02.2011 13:30, schrieb Dan Davison:
> Bernd Weiss<bernd.weiss@uni-koeln.de> writes:
[...]
>> Since I have two code blocks, I need to use :session. If I define
>> :session buffer-wide as
>>
>> #+BABEL: :session *R*
>>
>> then the matrix cormat is unknown within the second code block ("object
>> 'cormat' not found"). However, if I specify :session for each code block
>> seperately then it works as expected.
>
> Hi Bernd,
>
> The above does work for me. Some things to check:
>
> 1. After altering the #+BABEL line, it's necessary to refresh Org's
> file-local options, for example with C-c C-c on the #+BABEL
> line. (Same is true for #+OPTIONS, #+PROPERTY, etc)
>
> 2. I've just fixed a bug which was causing it to fail to work on the
> first attempt... But it did work on second and subsequent attempts.
>
> Please note that it is possible to make an equivalent setting using
>
> #+PROPERTY: session *R*
>
> In fact, I suspect we are going to drop #+BABEL entirely, so please
> consider it deprecated and use this form instead.
>
> After evaluating the first block, an ESS R buffer named *R* should
> exist, in which the variable cormat should be defined. Let me know if
> your problem persists.
Hi Dan,
Thanks for your reply. Using
#+PROPERTY: session *R*
(and running another =git pull origin master=) solved all my problems.
Thanks,
Bernd
prev parent reply other threads:[~2011-02-12 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:47 [Babel][R] buffer-wide and code block specific use of :session Bernd Weiss
2011-02-12 18:30 ` Dan Davison
2011-02-12 20:42 ` Bernd Weiss [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=4D56F0C4.1020500@uni-koeln.de \
--to=bernd.weiss@uni-koeln.de \
--cc=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).