emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Neuwirth Erich <erich.neuwirth@univie.ac.at>
Cc: "emacs-orgmode@gnu.org emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Inline and executing the document
Date: Thu, 20 Sep 2012 08:33:07 -0600	[thread overview]
Message-ID: <87vcf84vdo.fsf@gmx.com> (raw)
In-Reply-To: <16F6A604-26D2-47CA-9E12-A7E5F17FF737@univie.ac.at> (Neuwirth Erich's message of "Thu, 20 Sep 2012 16:23:38 +0200")

Neuwirth Erich <erich.neuwirth@univie.ac.at> writes:

> Sorry for not reading the docs carefully enough.
> I had overlooked :results wrap
> But even with this options things behave strangely.
> src_emacs-lisp[:results wrap]{(+ 2 3)} :RESULTS:
> 5:END:
> 5:END:
> 5:END:
> 5:END:
> 5:END:

Inline code blocks are only meant for execution during export.  They
were added so that results of code blocks could be inserted inline in
blocks of prose.  An example like the above should use a regular code

I would not be surprised if the manual is insufficiently clear on this
point.  If you could suggest a placement where wording such as the above
would have been helpful please let me know and I'll update the manual.


> Running the code multiple times in the document produces multiple outputs.
> I though the whole idea of wrapping was intended to mark results in a way the are replaces
> when the command is reexecuted.
> Furthermore, on exporting the keywords :RESULTS: and :END:
> are written into the exported document (I tried LaTeX+pdf and HTML)
> Am I still misunderstanding something?

Eric Schulte

  reply	other threads:[~2012-09-20 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 13:44 Inline and executing the document Erich Neuwirth
2012-09-19 14:09 ` Eric Schulte
2012-09-20 14:23 ` Neuwirth Erich
2012-09-20 14:33   ` Eric Schulte [this message]
2012-09-20 19:09   ` Neuwirth Erich
2012-09-23 17:02     ` Erich Neuwirth
2012-09-23 18:17       ` Bastien

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:

  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=87vcf84vdo.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=erich.neuwirth@univie.ac.at \


* 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


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).