John Kitchin <jkitc...@andrew.cmu.edu> writes: > Try this: > > #+BEGIN_SRC emacs-lisp > (defadvice org-babel-execute-src-block (around progress nil activate) > "create a buffer indicating what is running" > (let ((code-block (org-element-property :name (org-element-at-point))) > (cb (current-buffer))) > (split-window-below) > (other-window 1) > (switch-to-buffer "*My Babel*") > (insert (format "Running %s" code-block)) > (other-window 1) > ad-do-it > (kill-buffer "*My Babel*") > (delete-other-windows))) > #+END_SRC > > It will mess with your windows a bit, but it does what you want I think. >
Wouldn't a (message (format "Running %s" code-block)) be enough? That would avoid all the window munging. > > Gary Oberbrunner <ga...@oberbrunner.com> writes: > >> I have an org-mode babel program/document that takes about half an >> hour to run (end result is a LaTeX or HTML doc with figures). It's a >> mix of SQL and python. (The SQL is the slow part.) I'd really like it >> if org-mode could tell me, while it's running, which named block it's >> processing. Is there anything like that available? An option perhaps? -- Nick
