Hi Eric,

thanks for your answer.

Just for me to understand:  What is your suggestion then, if I still
want the source code block to be evaluated during export?
I asked a while ago on this list how to do that and got the answer
":exports results :results silent" which to my understanding now makes
perfectly sense:
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg36910.html

I tried to omit the ":exports results" header argument and got weirder
results, as now the #+call: is not evaluated at all, but appears in the
output.

===example to export===================
* Test1
  #+srcname: test
  #+begin_src R :session :results silent
    1:10
  #+end_src

  Test1.

* Test2
  #+call: test() :session :results silent

  Test2.
==================================

Best wishes,
Andreas



Am 14.03.2011 21:59, schrieb Eric Schulte:
> Hi Andreas,
>
> The ":exports results" header argument is overriding the ":results
> silent" header argument, which IMO is desired behavior.  Thanks to your
> example I see this is not the case for regular code blocks.  I would
> think that the behavior should be changed for regular code blocks,
> s.t. both of the tests in your example below export results.
>
> Best -- Eric
>
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>   
>> Hi everyone,
>>
>> Just pulled the latest HEAD and found that there is a regression in
>> babel.  When a source block is evaluated via #+call the :results silent
>> header arguement is ignored during export
>>
>> =test file====================================
>> * Test1
>>   #+srcname: test
>>   #+begin_src R :session :exports results :results silent
>>     1:10
>>   #+end_src
>>
>>   Test1.
>>
>> * Test2
>>   #+call: test() :session :exports results :results silent
>>
>>   Test2.
>> ==========================================
>>
>> Regards,
>> Andreas
>>     
>