From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] src_blocks - :results raw and replace don't work together
Date: Mon, 28 Jul 2014 16:46:02 +0200 [thread overview]
Message-ID: <87wqaxlexh.fsf@gmail.com> (raw)
In-Reply-To: 86ha21twha.fsf@somewhere.org
Sebastien Vauban <sva-news@mygooglest.com>
writes:
> Thorsten Jolitz wrote:
>> Nick Dokos <ndokos@gmail.com> writes:
>>
>>> Thorsten Jolitz <tjolitz@gmail.com>
>>> writes:
>>>
>>>> Hi List,
>>>>
>>>> evaluating this 3 times does not work as expected:
>>>>
>>>> ,----
>>>> | * A
>>>> |
>>>> | #+header: :results raw replace
>>>> | #+begin_src emacs-lisp
>>>> | (+ 2 2)
>>>> | #+end_src
>>>> |
>>>> | #+results:
>>>> | 4
>>>> | 4
>>>> | 4
>>>> `----
>>>>
>>>> Independent from argument order, 'replace' (which should be default
>>>> anyway) is ignored.
>>>
>>> Right - `raw' inserts results without delimiters so org has no idea
>>> where they end and cannot delete them (try org-babel-remove-result)
>>> or replace them.
>>
>> ok, I see
>>
>> from `org-babel-remove-result':
>> ,----
>> | (when (looking-at (concat org-babel-result-regexp ".*$")) ...)
>> `----
>>
>> seems a bit tricky to adapt this to 'raw results ...
>>
>> But at least there should be a hint in the manual that ':results raw
>> replace' is not supposed to work, and what would be a possible
>> workaround.
>
> Workarounds:
>
> - A block wrapper makes it possible for the entirety of the results to
> be clearly located, regardless of their contents, and replaced (with
> new results) by Babel upon code block re-evaluation, or
>
> - :results drawer
Thx. I somehow remember that my problem was related to the recently
discussed issue of creating new headlines as results of source blocks,
and to the fact that only headlines can contain headlines, so wrapping
in blocks and drawers does not really work.
I finally solved that problem for me by simply inserting the new headers
from Emacs Lisp without using Org-Babel, although a few workarounds were
proposed in the mentioned thread on this mailing list (a real solution
too? unfortunately lost track ...).
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-07-28 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 0:28 [BUG] src_blocks - :results raw and replace don't work together Thorsten Jolitz
2014-07-07 1:41 ` Thomas S. Dye
2014-07-07 2:03 ` Thorsten Jolitz
2014-07-07 13:48 ` Thomas S. Dye
2014-07-07 9:29 ` Andreas Leha
2014-07-07 10:15 ` Thorsten Jolitz
2014-07-07 11:04 ` Thorsten Jolitz
2014-07-07 11:16 ` Andreas Leha
2014-07-07 11:59 ` Thorsten Jolitz
2014-07-07 13:56 ` Nick Dokos
2014-07-07 14:54 ` Grant Rettke
2014-07-07 15:31 ` Thorsten Jolitz
2014-07-07 23:40 ` Grant Rettke
2014-07-08 2:01 ` Nick Dokos
2014-07-07 15:40 ` Thorsten Jolitz
2014-07-28 13:59 ` Sebastien Vauban
2014-07-28 14:46 ` Thorsten Jolitz [this message]
2014-08-04 1:20 ` Eric Schulte
2014-08-06 1:15 ` Thorsten Jolitz
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=87wqaxlexh.fsf@gmail.com \
--to=tjolitz@gmail.com \
--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).