emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] feature request: automatically connect source code block to its session
Date: Sat, 02 Apr 2011 11:48:51 -0600	[thread overview]
Message-ID: <87mxk8v918.fsf@gmail.com> (raw)
In-Reply-To: <4D8C95F6.5040304@med.uni-goettingen.de> (Andreas Leha's message of "Fri, 25 Mar 2011 14:17:42 +0100")

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Hi Eric,
> thanks for looking into this!
> Unfortunately, I do not know the setup here.  But I asked on the ess
> mailing list and got an answer from Stephen Eglen:
> "I think you want to set ess-local-process-name given by the :session
> argument in the .org buffer when the temp buffer is opened by C-c '."
> I hope that is the information you need.

I opened up a example.R buffer, evaluated some code, and a session named
"*R*" was created and the value of `ess-local-process-name' was set to
"R", so I've just pushed up a patch which will set the value of
`ess-local-process-name' to "something" if the value of the :session
header is "*something*", it will also start the session if none exists.

Please let me know if this give the desired result.  If not, then could
you point me to an ESS feature which uses the associated session which I
could use locally to test?

Note also, that this patch adds a general facility through which any
language can prep an org edit src buffer through the definition of a
org-babel-edit-prep:lang function, which will be passed the full info
list for the code block.  If there are any other languages which would
benefit from edit-buffer initialization it should now be a simple task
to implement such initialization.

Thanks -- Eric

> Regards,
> Andreas
> Am 23.03.2011 04:00, schrieb Eric Schulte:
>> 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 <andreas.leha@med.uni-goettingen.de> 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
>>> session.
>>> 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
>>> buffer-local")
>>> and this way cuts the connection to org, such that C-' becomes undefined.
>>> Regards,
>>> Andreas

      reply	other threads:[~2011-04-02 17:49 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
2011-03-25 13:17   ` Andreas Leha
2011-04-02 17:48     ` Eric Schulte [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:

  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=87mxk8v918.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \


* 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).