From: Erik Iverson <eriki@ccbr.umn.edu>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: [babel] possible bug in org-babel-execute-buffer?
Date: Wed, 26 May 2010 18:59:10 -0500 [thread overview]
Message-ID: <4BFDB5CE.3010600@ccbr.umn.edu> (raw)
Hello,
I am using Emacs 23.1, orgmode pulled from git just an hour ago, but I noticed
the following issue on a version pulled about a week ago, too. I don't know if
it ever worked as I expect. These development versions have C-c C-v as the
babel prefix keys, so if you are using a stable version, the following may be
different. Also, all my examples use R.
I'm trying to use C-c C-v C-b to call org-babel-execute-buffer, which is
documented as:
Call `org-babel-execute-src-block' on every source block in
the current buffer.
However, what happens when this is called seems to depend on which trees are
visible in the buffer when it's called!
Paste the following orgmode file into an org buffer, and make sure all trees are
fully collapsed, i.e., you just see the headlines "Big Block 1" and "Big Block
2", and try C-c C-v C-b.
After it's done executing, notice that only the *last* source blocks of each
tree were run. Now collapse everything again, and call org-babel-execute-buffer
again. The same thing happens, except now there are *two* results present for
those last code blocks.
Now start all over again with the below code, so no results are present. Expand
all subtrees so everything is visible. Do C-c C-v C-b, and all results are
inserted as expected. Run the blocks a second time with everything open, and
every block still only has 1 results section, as expected. This is how I would
expect/hope the function to work regardless of the hide/show states of the trees.
So I think there are two possibly related problems when trees aren't fully
expanded:
1) Only the last source code block per hidden tree is getting run
2) That last block will insert results multiple times if
org-babel-execute-buffer is called multiple times
Thanks!
Erik
=================== orgmode code follows below ======================
* Big Block 1
** my first bit of code!
#+begin_src R
"from the first nested code block in Big Block 1"
#+end_src
** and some more code!
#+begin_src R
"from the middle nested code block in Big Block 1"
#+end_src
** and final code!
#+begin_src R
"from the final nested code block in Big Block 1"
#+end_src
* Big Block 2
#+begin_src R
"from the only code block in Big Block 2"
#+end_src
next reply other threads:[~2010-05-26 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 23:59 Erik Iverson [this message]
2010-05-27 1:45 ` [babel] possible bug in org-babel-execute-buffer? Eric Schulte
2010-05-27 4:54 ` Erik Iverson
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=4BFDB5CE.3010600@ccbr.umn.edu \
--to=eriki@ccbr.umn.edu \
--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).