From: "Eric Schulte" <schulte.eric@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel][Bug] results silent ignored in #+call
Date: Tue, 15 Mar 2011 07:13:50 -0600 [thread overview]
Message-ID: <87wrk034s1.fsf@gmail.com> (raw)
In-Reply-To: <4D7F0BA1.7010201@med.uni-goettingen.de> (Andreas Leha's message of "Tue, 15 Mar 2011 07:48:01 +0100")
Hi Andreas,
If the call line has a ":session" header argument, then it should be
evaluated on export; regardless of the value of the ":export" header
argument. Adding a ":exports none" header argument, should inhibit the
insertion of any results into the exported document.
In your example below, the reason that the #+call: header argument is
not exported is because your :session header argument has no value, the
following call line would be exported.
#+call: test() :session *R* :exports none
I just pushed up a fix which removes this requirement for named
sessions, so you example below should now work.
Best -- Eric
Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
> 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
>>>
>>
next prev parent reply other threads:[~2011-03-15 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 20:07 [Babel][Bug] results silent ignored in #+call Andreas Leha
2011-03-14 20:59 ` Eric Schulte
2011-03-15 6:48 ` Andreas Leha
2011-03-15 13:13 ` Eric Schulte [this message]
2011-03-15 15:09 ` Andreas Leha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrk034s1.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).