emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Babel more verbose?
Date: Tue, 02 Sep 2014 10:54:35 -0400	[thread overview]
Message-ID: <878um2dqdw.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: m2zjeijeh1.fsf@andrew.cmu.edu

John Kitchin <jkitchin@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 <garyo@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

  reply	other threads:[~2014-09-02 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 12:32 Babel more verbose? Gary Oberbrunner
2014-09-02 14:15 ` John Kitchin
2014-09-02 14:54   ` Nick Dokos [this message]
2014-09-02 15:01     ` David Wagle
2014-09-02 17:23       ` Grant Rettke
2014-09-05 13:20       ` Gary Oberbrunner
2014-09-02 17:30     ` John Kitchin
2014-09-03  3:58       ` Nick Dokos

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=878um2dqdw.fsf@alphaville.bos.redhat.com \
    --to=ndokos@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).