From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: cleaning all the #+results from an org document
Date: Fri, 29 Jul 2011 10:38:58 -0600 [thread overview]
Message-ID: <878vrhnij5.fsf@gmail.com> (raw)
In-Reply-To: 804o255wqg.fsf@somewhere.org
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Eric,
>
> "Sebastien Vauban" wrote:
>> Eric Schulte wrote:
>>> Ista Zahn <izahn@psych.rochester.edu> writes:
>>>> On Thu, Jul 28, 2011 at 8:59 AM, Stephen Eglen
>>>> <S.J.Eglen@damtp.cam.ac.uk> wrote:
>>>>> Thanks Torsten, you've expressed it elegantly!
>>>>>>
>>>>>> c) to delete all the old results and start "fresh"
>>>>
>>>> +1 for c. I often work with R objects that are simply too large to store
>>>> in org tables, so I use babel caching + session + write / load R data
>>>> files from disk. This works, but it becomes easy to get to an inconsistent
>>>> state, and I would like to be able to delete the results blocks and run
>>>> the whole thing fresh.
>>>
>>> You could try evaluating the following with "M-x :" in an Org-mode buffer.
>>>
>>> #+begin_src emacs-lisp
>>> (org-babel-map-src-blocks nil (org-babel-remove-result))
>>> #+end_src
>>
>> On the file I took for testing, this works OK.
>
> More complete test...
>
> * Test 1 -- OK!
>
> ** Anonym block
>
> #+begin_src emacs-lisp :results output org
> (print "Test")
> #+end_src
>
> #+results:
> #+BEGIN_ORG
>
> "Test"
> #+END_ORG
>
> ** Named block
>
> #+source: echo
> #+begin_src emacs-lisp :var n="me"
> (message "hi %s" n)
> #+end_src
>
> #+results: echo
> : hi me
>
> * Test 2 -- OK!
>
> Setting a global data through a fake results block:
>
> #+results: max-lines
> : 200
>
> Then using it:
>
> #+source: print-max-lines
> #+begin_src emacs-lisp :var n=max-lines
> (message "there are %s lines" n)
> #+end_src
>
> #+results: print-max-lines
> : there are 200 lines
>
> The latter results block is deleted. The former, with the assignation, is not.
> Excellent!
>
> * Test 3 -- Not OK... <<<
>
> And the call line for the named block:
>
> #+call: echo()
>
> #+results: echo()
> : hi me
>
> This results block is not deleted, while it should?
>
Thanks,
I've just pushed up a new interactive function `org-babel-kill-results'
which deletes code block results, inline code block results, and call
line results.
>
>> Regarding a key binding, looking at =C-c C-v h=, this is already quite full.
>> Though, =k= is free, and could be used for "killing the results".
>
Sounds good to me, the above function is now bound to "C-c C-v k". If
called w/o a prefix argument it only applies to the current code block,
when called with a prefix argument it applies to the entire buffer.
Best -- Eric
>
> Best regards,
> Seb
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-07-29 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 8:31 cleaning all the #+results from an org document Stephen Eglen
2011-07-28 9:21 ` suvayu ali
2011-07-28 11:41 ` Stephen Eglen
2011-07-28 11:58 ` suvayu ali
2011-07-28 11:41 ` Sebastien Vauban
2011-07-28 12:24 ` Torsten Wagner
2011-07-28 12:59 ` Stephen Eglen
2011-07-28 16:15 ` Ista Zahn
2011-07-28 23:04 ` Eric Schulte
2011-07-29 7:48 ` Sebastien Vauban
2011-07-29 8:15 ` Sebastien Vauban
2011-07-29 16:38 ` Eric Schulte [this message]
2011-07-29 14:42 ` Torsten Wagner
2011-07-29 16:40 ` Eric Schulte
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=878vrhnij5.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).