[ESS] ESS: running blocks of script very slow
Kasper Daniel Hansen
kasperdanielhansen at gmail.com
Fri Mar 4 01:59:41 CET 2011
The slowdown has certainly been there for the last 5 years. I have
always thought it had to do with fontification of the *R* buffer, but
that is pure speculation.
Personally, aside from the speedup, I like the behavior of
ess-eval-visibly-p. And one could argue, that if you believe in "the
source code is real", you do not care about keeping track of what is
being sent to the *R* buffer. My only problem with the behaviour is
that it currently does something like
where I would really like
or perhaps ++++ exchanged with something like <SNIP>.
However, getting back to the discussion, I can see that some people
would prefer to see the entire output. And turning it off purely for
speed reasons seems to be less desirable. Having said that, I have no
idea on how to start fixing it.
On Thu, Mar 3, 2011 at 7:39 PM, Paul Johnson <pauljohn32 at gmail.com> wrote:
> On Thu, Mar 3, 2011 at 2:22 PM, Matthew Landis <landis at isciences.com> wrote:
>> I guess for no other reason than that's what I'm used to. But sometimes I
>> move the point and forget what exactly I submitted. It's a very minor
>> issue, and certainly the advantages of ESS far outweigh this minor
>> Matthew Landis, Ph.D.
>> Research Scientist
> I think Matthew is right. We shouldn't let him back down.
> This proposal makes it impossible to track a project.
> For record keeping and transmission of material to other people, it is
> very important to me to have 'what actually ran' in the same file with
> the results. Perhaps Vitalie is still able to remember all of the
> commands he has ever run and can link them with the output sections of
> various files. But I can't.
> Turning off the commands in the output file is, well, throwing out too
> much. Sometimes I'm working on something and save the output file and
> later wonder "what did I do that caused that"? And I can read the
> code. Or somebody sends me something, and I wonder how they get it?
> I can't say how it looks on your system, but when I use
> (setq ess-eval-visibly-p nil)
> The R output buffer still shows individual lines that are sent to R,
> but just not regions. So it produces a very horrible record of what
> Now here's my question. Has this slowdown always been there? I don't
> think I noticed it until about 8 or 10 months ago. It is about the
> same time that Sweave started giving the ESS process not ready error.
> Is there a common cause?
> Paul E. Johnson
> Professor, Political Science
> 1541 Lilac Lane, Room 504
> University of Kansas
> ESS-help at r-project.org mailing list
More information about the ESS-help