From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Rettke Subject: Re: Babel more verbose? Date: Tue, 2 Sep 2014 12:23:36 -0500 Message-ID: References: <878um2dqdw.fsf@alphaville.bos.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOrnx-0003xy-6k for emacs-orgmode@gnu.org; Tue, 02 Sep 2014 13:23:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOrnt-0005OV-O4 for emacs-orgmode@gnu.org; Tue, 02 Sep 2014 13:23:41 -0400 Received: from mail-oa0-x231.google.com ([2607:f8b0:4003:c02::231]:36440) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOrnt-0005OF-If for emacs-orgmode@gnu.org; Tue, 02 Sep 2014 13:23:37 -0400 Received: by mail-oa0-f49.google.com with SMTP id jd19so5017202oac.22 for ; Tue, 02 Sep 2014 10:23:36 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: David Wagle Cc: "emacs-orgmode@gnu.org" I am curious about how to get more reporting when tangling is occurring because I would like to narrow down what parts of my document are slow to tangle so that I can refactor them and speed it up. Grant Rettke | ACM, ASA, FSF gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/ =E2=80=9CWisdom begins in wonder.=E2=80=9D --Socrates ((=CE=BB (x) (x x)) (=CE=BB (x) (x x))) =E2=80=9CLife has become immeasurably better since I have been forced to st= op taking it seriously.=E2=80=9D --Thompson On Tue, Sep 2, 2014 at 10:01 AM, David Wagle wrote: > It sounds like perhaps the issue is code blocks with a long run-time that > may or may not fail or hang in some way? > > If that's the case, the solution is probably simply breaking up your code > blocks into smaller bits of code so that you more easily follow what's > happening. > > If the code is emacs-lisp, it's easy enough to put (message ...) calls > entering and leaving the code blocks. > > > On Tue, Sep 2, 2014 at 9:54 AM, Nick Dokos wrote: >> >> John Kitchin 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 thin= k. >> > >> >> Wouldn't a (message (format "Running %s" code-block)) be enough? >> That would avoid all the window munging. >> >> > >> > Gary Oberbrunner 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 >> >> >