[Top][All Lists]

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

Re: [O] Bug? R: Org babel block execution *drastically* slower than in E

From: John Hendy
Subject: Re: [O] Bug? R: Org babel block execution *drastically* slower than in ESS session directly
Date: Fri, 16 Nov 2012 13:00:50 -0600

On Fri, Nov 16, 2012 at 11:47 AM, Andreas Leha <address@hidden> wrote:
Hi Eric,

Eric Schulte <address@hidden> writes:

> Andreas Leha <address@hidden> writes:
>> address@hidden (Thomas S. Dye) writes:
>>> Aloha Aaron,
>>> Welcome to Org-mode.
>>> Aaron Ecay <address@hidden> writes:
>>>> 2012ko azaroak 13an, John Hendy-ek idatzi zuen:
>>>> [...]
>>>>> Crazy. I really wondered if it had something to do with trying to spit
>>>>> out the results into the minibuffer. Why is that behavior included?
>>>> “:results silent” just means “silent except for the minibuffer”; IDK
>>>> why.
>> [...]
>> Just for the record:
>> I would also love to see the "really-silent results".
> Yes, the existing ":results silent" option still echos the results to
> the minibuffer.  It was originally added in the case where one does not
> want to change the Org-mode buffer (but would still like to see code
> block output).
> The attached patch adds a "really-silent" results header argument.  To
> see the impact compare the running time of the following two code
> blocks.
>     #+begin_src sh :results really-silent
>       seq 100000000
>     #+end_src
>     #+begin_src sh :results silent
>       seq 100000000
>     #+end_src
> Before such a patch is applied it would need corresponding
> documentation, and the "really-silent" moniker may need to be
> reconsidered in favor of something more informative (the main purpose of
> this header argument is not silence but is rather avoiding all post
> processing), and ideally shorter as well.  These new header arguments
> are of no value if they are not easily discover-able and easily
> remember-able to help others avoid the same issue that launched this
> thread.
> Cheers,

this is simply great!  Thank a lot.  I just tested and like it a lot!

I'll have to give this a try.
With respect to the name: I think choosing a new name is hard because it
really should be "silent".  What is now "silent" would better be named
"minibuffer" or sth. similar.  But since changing that would break quite
some (of my) code, I would suggest simply "none" for the new

I like the "none" idea. Or another approach would be a variable/in-buffer setting that defines the meaning of "silent"? Something like =org-babel-echo-results-in-minibuffer= or something like that? Though perhaps folks would like to mix and match silent and none within the same document.

Thanks for creating the patch, Eric. I'll try shortly.

Best regards,

Just my 2ct.

Thanks again.  I'll start using it right now.


reply via email to

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