From: "Eric Schulte" <firstname.lastname@example.org>
To: Andreas Leha <email@example.com>
Subject: Re: [babel] feature request: automatically connect source code block to its session
Date: Tue, 22 Mar 2011 21:00:20 -0600 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
This seems reasonable,
Do you know how ESS associates a code buffer with a session (i.e. is
there some buffer-local variable which holds the session name)?
With this information in hand it shouldn't be difficult to expand the
C-' behavior for R s.t. it automatically associates the resulting
Org-Src buffer with the proper R session.
Good idea. Best -- Eric
Andreas Leha <email@example.com> writes:
> Hi all,
> I have a feature request (if what I want is not already possible, that is).
> Could a source code block, which has the :session header argument, be
> associated with its session as soon as C-' is pressed?
> The background to this question is, that all ess support functionality
> for R (r-autoyas, autocomplete-R, and ess-eldoc) need an associated R
> session. They start to function only as soon as the first line of the
> code block is evaluated, which associates the source buffer with its
> The autocomplete-R even fails to load without an associated R session
> (byte-code: Language mode `R-mode' fails with: "Symbol nil may not be
> and this way cuts the connection to org, such that C-' becomes undefined.
next prev parent reply other threads:[~2011-03-23 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 15:19 [babel] feature request: automatically connect source code block to its session Andreas Leha
2011-03-23 3:00 ` Eric Schulte [this message]
2011-03-25 13:17 ` Andreas Leha
2011-04-02 17:48 ` Eric Schulte
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).