Eric Schulte <
schulte.eric@gmail.com> writes:
> Andreas Leha <
andreas.leha@med.uni-goettingen.de> writes:
>
>>
tsd@tsdye.com (Thomas S. Dye) writes:
>>
>>> Aloha Aaron,
>>>
>>> Welcome to Org-mode.
>>>
>>> Aaron Ecay <
aaronecay@gmail.com> 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,