Hi Erich,
Erich Neuwirth writes:
> One more thought:
> The :RESULTS: :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 docu
One more thought:
The :RESULTS: :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 de
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 wrote:
> Sorry for not reading the docs carefully enough.
> I had overlooked :results wrap
> But even with this options things behave str
Neuwirth Erich 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:
> :RESULTS:
> 5:END:
> :RESULTS:
> 5:END:
> :RESULTS:
> 5:END:
> :RESULTS:
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:
:RESULTS:
5:END:
:RESULTS:
5:END:
:RESULTS:
5:END:
:RESULTS:
5:END:
Running the code multiple times in the d
Erich Neuwirth writes:
> The following examples shows some issues
>
All of these examples execute as expected. It is not always possible to
automatically identify and remove the results of a code block execution.
Remember that Org-mode files are just plain text.
>
> #+title: Inline formatting
