Re: [babel] feature request: debug messages

[Eric Schulte <schulte.eric@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 164 bytes --]

Hi Andreas,

This should be easy to turn on or off using the newly introduced
:prologue and :epilogue header arguments.  See the manual and the
following example.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: r-debug.org --]
[-- Type: text/x-org, Size: 739 bytes --]

#+Title: debug messages
#+Property: session *R*
#+Property: prologue (format "print(\"entering %s\")" (get-current-name))

An elisp block to simplify the =:prologue= definition.
#+begin_src emacs-lisp
  (defun get-current-name ()
    (save-excursion
      (goto-char org-babel-current-src-block-location)
      (while (and (forward-line -1)
                  (looking-at org-babel-multi-line-header-regexp)))
      (when (looking-at org-babel-src-name-w-name-regexp)
        (org-no-properties (match-string 3)))))
#+end_src

Two blocks with simple assignments.

#+name: block-1
#+begin_src R
  x <- 2 + 2
#+end_src

#+name: block-2
#+begin_src R
  y <- x + x
#+end_src

Execute the whole buffer =C-c C-v b= to see the prologue in action.

[-- Attachment #3: Type: text/plain, Size: 1037 bytes --]


Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Hi all,
>
> I would love to see messages like 'entering block foo...' and
> '...leaving block foo' printed to my R console.  This would be very
> handy when I evaluate a subtree (C-c C-v s) with a lot of #+call lines
> and some lengthy ones.
>
> I know that
> (1) I could implement that myself at in the source blocks.  But I would
>     love if orgmode did that for me
> (2) Such messages are already printed to the emacs *Messages* buffer.
>     But that buffer might not be visible and I can not switch to it,
>     without interrupting the evaluation.  Anyway it would be much nicer
>     to see that output together with the other output, that my code
>     generates.
>
>
> In essence it would be very helpful, if there was a variable
> org-babel-print-debug-messages (or org-babel-debug-level...) which if
> non-nil would cause that messages to be printed.  Or is there somewhere
> already?
>
> Regards,
> Andreas
>
>
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte