From: "Charles C. Berry" <ccberry@ucsd.edu>
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: "'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 <at> /usr/local/share/emacs/site-lisp/org/)]
Date: Thu, 18 Sep 2014 15:34:45 -0700 [thread overview]
Message-ID: <alpine.OSX.2.00.1409181519530.1863@charles-berrys-macbook.local> (raw)
In-Reply-To: <D4772401B9D976478C0895769BE3E7920F1EE71B@MBSRV02.sgc.loc>
On Thu, 18 Sep 2014, Cook, Malcolm wrote:
> Hi,
>
> Hmm, I spoke too soon.... the problem is only partially fixed by this patch...
>
> Trying to work with in org-mode with R code blocks attached to
> persistent sessions (i.e. adding ':session myRsession' to the code block
> header ) makes things start to break again, at least in my hands.
Really? I have been working for hours using the :session header with no
problems.
What exactly breaks? Do you have an example?
FWIW, this works when I move my cursor into the source block and C-c C-c.
--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC R :session myRsession
abc <- 1
abc+1
#+END_SRC
--8<---------------cut here---------------end--------------->8---
Producing
--8<---------------cut here---------------start------------->8---
#+RESULTS:
: 2
--8<---------------cut here---------------end--------------->8---
which is what I expect.
I use Org-mode version 8.3beta (release_8.3beta-366-gb2fca7.
(updated a few hours back)
>
> I'm going to wait till things settle down before trying to upgrade ESS again.
It would really help to be sure that this is not a problem with your
setup. And if you can give a simple example that shows the problem, I'd
appreciate it.
BTW, how does a 'persistent' session differ from all those other sessions?
Chuck
next prev parent reply other threads:[~2014-09-18 22:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 20:16 Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 @ /usr/local/share/emacs/site-lisp/org/)] Ed Kademan
2014-09-16 13:03 ` Rainer M Krug
2014-09-16 20:17 ` Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 <at> /usr/local/share/emacs/site-lisp/org/)] Charles Berry
2014-09-17 3:25 ` [PATCH] WAS " Charles Berry
2014-09-17 7:20 ` Rainer M Krug
2014-09-17 7:26 ` Rainer M Krug
2014-09-17 23:14 ` Cook, Malcolm
[not found] ` <D4772401B9D976478C0895769BE3E7920F1ED33C@MBSRV02.sgc.loc>
2014-09-18 21:13 ` Cook, Malcolm
2014-09-18 21:27 ` Aaron Ecay
2014-09-19 7:50 ` Rainer M Krug
2014-09-18 22:34 ` Charles C. Berry [this message]
2014-09-18 22:45 ` Charles C. Berry
2014-10-07 19:34 ` Henrik Singmann
2014-10-07 21:17 ` Ista Zahn
2014-10-08 1:59 ` Charles Berry
2014-10-08 1:21 ` Charles Berry
2014-10-08 9:57 ` Henrik Singmann
2014-10-10 4:38 ` Aaron Ecay
2014-10-10 9:18 ` Henrik Singmann
2014-10-10 16:36 ` Aaron Ecay
2014-12-09 21:07 ` Cook, Malcolm
2014-09-18 1:17 ` Aaron Ecay
2014-09-18 15:17 ` Charles C. Berry
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=alpine.OSX.2.00.1409181519530.1863@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=MEC@stowers.org \
--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).