From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] export of inline source with wrapped results
Date: Tue, 08 May 2012 22:24:13 +0200 [thread overview]
Message-ID: <87ehqu2zgy.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87d36eimig.fsf@gmx.com
Eric Schulte <eric.schulte@gmx.com> writes:
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> Hi all,
>>
>> I experience a problem when exporting the results of inline source
>> blocks when they are wrapped: the export (using the "old" latex
>> exporter) contains ":RESULTS:" and ":END:"
>>
>> Here is an example src_R[:results org wrap]{tmp <- "inline"} call.
>>
>> And the LaTeX export of this is
>> #+begin_latex
>> Here is an example :RESULTS:
>> inline:END:
>> call.
>> #+end_latex
>>
>> Is this a known bug?
>>
>> Regards,
>> Andreas
>>
>
> What would you expect to see?
>
> I don't it was ever anticipated that anyone would wrap inline results.
>
> Best,
Hi Eric,
thanks for this fast response.
I would expect *not* to see the ":RESULTS:", ":END:" in the export. I
consider them "org mode internal" just like "#+begin_src ... #+end_src"
and can't see a use of them being in the exported document.
Why would I wrap inline results? Good question. It has been quite
useful, but it seems that use has gone.
The problem I was trying to tackle with the wrapping is that of multiple
executions of an inline source block leading to multiple results.
Like I executed this twice: src_R{1} =1= =1=.
I think once wrapping was a solution to this, but maybe I am wrong here.
In any case, now it isn't:
Again executed twice: src_R[:results wrap]{1} :RESULTS:
1:END:
:RESULTS:
1:END:
So, here is the follow-up question: How to make inline replace their
results (as other code blocks do)?
Regards,
Andreas
prev parent reply other threads:[~2012-05-08 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 19:38 [babel] export of inline source with wrapped results Andreas Leha
2012-05-08 17:52 ` Eric Schulte
2012-05-08 20:24 ` Andreas Leha [this message]
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=87ehqu2zgy.fsf@med.uni-goettingen.de \
--to=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).