emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] BUG: emacs orgmode ob-R.el function org-babel-R-evaluate-session


From: Charles C. Berry
Subject: Re: [O] BUG: emacs orgmode ob-R.el function org-babel-R-evaluate-session over aggressively performs "; ; cleanup extra prompts left in output" and a possible workaround
Date: Thu, 8 Oct 2015 12:24:08 -0700
User-agent: Alpine 2.20 (OSX 67 2015-01-07)

On Thu, 1 Oct 2015, Cook, Malcolm wrote:

I am not sure what the best solution is, but, in my hands using
> > Org-mode version 8.3.2-elpa org-20150929 the reg-expt used to "cleanup
> > extra prompts left in output" is over-aggressive and will trim session
> > :output at lines consisting exclusively of blanks and periods such as
> > produced when printing a BioConductor 'Views' object which wants to
> > appear as
>

[snip]

I offer as a possible workaround the following:
> >
> > So far, I have had good success having removed provision for allowing
> leading whitespace by changing the regexp  org-babel-R-evaluate-session
> from
> >      "^\\([ ]*[>+\\.][ ]?\\)+\\([[0-9]+\\|[ ]\\)"
> > to
> >      "^\\([>+\\.][ ]?\\)+\\([[0-9]+\\|[ ]\\)"
> >
> > But I don't know all the test cases so, YMMV....

I have traced this back to its source, and the culprit appears to be me.

See
  commit dc92eaa08d89e4bc9556f868ae65633196157a8d
  Author: Eric Schulte <address@hidden>
  Date:   Wed Jul 28 08:05:30 2010 -0600
and subsequent modifications.

I believe the leading blank(s) in the regex were copied from ess, but nowadays I only see this in code in ess-traceback.el that is commented out.

So I guess there would be no harm in pushing the latter regex.

Chuck



reply via email to

[Prev in Thread] Current Thread [Next in Thread]