Hi Seb,
Thanks for this patch, I've applied it and then tweaked the wording of
the message.
Best,
"Sebastien Vauban" <sva-n...@mygooglest.com> writes:
> Hello,
>
> Here is a small patch to improve the messages displayed by Org Babel when
> processing code blocks: now, you get the line number added to the output, so
> that you can easily find afterward which block had problems, if such things
> were reported in the *Messages* buffer.
>
> Best regards,
> Seb
>
> From 9e8b74d881575318ff480f084ac10aea82696904 Mon Sep 17 00:00:00 2001
> From: Sebastien Vauban <sva-n...@mygooglest.com>
> Date: Thu, 7 Nov 2013 16:24:53 +0100
> Subject: [PATCH] Improve "Processing Org code block" message
>
> * ob-exp.el (org-babel-exp-src-block): Improve message by adding line number.
>
> ---
> lisp/ob-exp.el | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/lisp/ob-exp.el b/lisp/ob-exp.el
> index c8479e3..3874338 100644
> --- a/lisp/ob-exp.el
> +++ b/lisp/ob-exp.el
> @@ -110,12 +110,14 @@ none ---- do not display either code or results upon
> export
>
> Assume point is at the beginning of block's starting line."
> (interactive)
> - (unless noninteractive (message "org-babel-exp processing..."))
> (save-excursion
> (let* ((info (org-babel-get-src-block-info 'light))
> + (line (org-current-line))
> (lang (nth 0 info))
> (raw-params (nth 2 info)) hash)
> ;; bail if we couldn't get any info from the block
> + (unless noninteractive
> + (message "Processing %s code block at line %d..." lang line))
> (when info
> ;; if we're actually going to need the parameters
> (when (member (cdr (assoc :exports (nth 2 info))) '("both" "results"))
> --
> 1.7.9
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
