emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Erich Neuwirth <erich.neuwirth@univie.ac.at>
To: "emacs-orgmode@gnu.org emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Inline and executing the document
Date: Sun, 23 Sep 2012 19:02:16 +0200	[thread overview]
Message-ID: <7C2CE242-C739-4343-B051-E2885BF4BB9A@univie.ac.at> (raw)
In-Reply-To: <BEF2884F-F677-41DB-A865-EEA3AAD93F3F@univie.ac.at>

One more thought:
The :RESULTS: xxxx :END:
wrapper would allow to replace when inline code is run once again.
It would fit with my personal workflow to be able to check what will go into the exported documents
while fiddling around in the source document.

If this does not fit with what the org designers think, thats OK.
I just wanted to note that the implementation replacement of results of inline code
in this special case could probably done with ease.


On Sep 20, 2012, at 9:09 PM, Neuwirth Erich <erich.neuwirth@univie.ac.at> wrote:

> Thank you,
> this clarified things for me!
> I will look and suggest a place for mentioning this in the docs.
> Erich
> On Sep 20, 2012, at 4:23 PM, Neuwirth Erich <erich.neuwirth@univie.ac.at> wrote:
>> 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:
>> 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?

  reply	other threads:[~2012-09-23 17:02 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
2012-09-20 19:09   ` Neuwirth Erich
2012-09-23 17:02     ` Erich Neuwirth [this message]
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=7C2CE242-C739-4343-B051-E2885BF4BB9A@univie.ac.at \
    --to=erich.neuwirth@univie.ac.at \
    --cc=emacs-orgmode@gnu.org \


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