From: Torsten Wagner <torsten.wagner@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Ista Zahn <izahn@psych.rochester.edu>,
Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>,
emacs-orgmode@gnu.org
Subject: Re: cleaning all the #+results from an org document
Date: Fri, 29 Jul 2011 23:42:57 +0900 [thread overview]
Message-ID: <4E32C6F1.2060503@gmail.com> (raw)
In-Reply-To: <871uxadk3v.fsf@gmail.com>
Hi Eric,
On 07/29/2011 08:04 AM, Eric Schulte wrote:
> #+begin_src emacs-lisp
> (org-babel-map-src-blocks nil (org-babel-remove-result))
> #+end_src
it works on my java stuff, but for some reason it creates a result by
itself in my system.
E.g.,
#+results:
: 508
There is another glitch...
The additional empty lines created by execution of a code block to
create the result section are not removed. Going forth and back creates
more and more empty lines.
#+begin_src sh
echo "No more empty rows"
#+end_src
* I am squeezed directly under the code block
execute it
#+begin_src sh
echo "No more empty rows"
#+end_src
#+results:
: No more empty rows
* I am squeezed directly under the code block
Remove the result with the given function
#+begin_src sh
echo "No more empty rows"
#+end_src
* I am squeezed directly under the code block
Execute the code again
#+begin_src sh
echo "No more empty rows"
#+end_src
#+results:
: No more empty rows
* I am squeezed directly under the code block
As for the key I like the C-c C-v k idea
What do you think about the (optional) timestamps idea for results ...
might be great for archiving. Open a file a year later and still be able
to see when you executed the blocks the last time might be helpful in
terms of "Ohhh yeah this was before I fixed this terrible bug"...
Greetings
Totti
next prev parent reply other threads:[~2011-07-29 14:43 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
2011-07-29 14:42 ` Torsten Wagner [this message]
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=4E32C6F1.2060503@gmail.com \
--to=torsten.wagner@gmail.com \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=izahn@psych.rochester.edu \
--cc=schulte.eric@gmail.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).