emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [Babel] Handling of errors when using Ledger
Date: Wed, 13 Oct 2010 09:04:52 +0100	[thread overview]
Message-ID: <87mxqiv7q3.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <807hhnfaix.fsf@mundaneum.com>

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

On Tue, 12 Oct 2010 21:58:46 +0200, Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> Hi Dan,
> 
> Dan Davison wrote:
> > Sébastien Vauban writes:
> > [...]
> >> Let's imagine I thought (which was the case at some point) I needed to
> >> enclose the parameters between quotes:
> >>
> >> #+srcname: quoted-params
> >> #+begin_src ledger :cmdline "reg unknown" :noweb yes :session
> >> <<data>>
> >> #+end_src
> >>
> >> #+results: quoted-params
> >>
> >> Nothing is returned. In fact, I would expect an error to be thrown [...] I
> >> don't know if this is a common problem (to Org-Babel) or only to the Ledger
> >> part of it, but I think *we* should somehow improve the handling of errors.
> >
> > Babel has a standard mechanism for evaluating shell commands and displaying
> > errors if any. It is the function `org-babel-eval' in ob-eval.el. The
> > problem is that ob-ledger is not using this mechanism. Would you be
> > interested in fixing this? Basically what is required is to re-implement
> > `org-babel-execute:ledger' using `org-babel-eval'. (There are plenty of
> > examples in the other langauges to follow.) Please don't worry if you are
> > too busy though.
> 
> I'd be interested to try and fix it. I am busy, yes: I am just recovering 3

[...]

> So, I'd propose to fight for being the first one to fix that... And let's see
> who will win... ;-)

Please do!!  As the original author (basing my code on other babel
codes, mind you), I am happy to lose this fight ;-)  I really don't
know enough babel to make the changes required quickly and I also am
struggling with "free" time at the moment.


[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

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

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-10-13 12:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 11:55 [Babel] Handling of errors when using Ledger Sébastien Vauban
2010-10-07 13:36 ` Dan Davison
2010-10-12 19:58   ` Sébastien Vauban
2010-10-13  8:04     ` Eric S Fraga [this message]
2010-11-25 16:32       ` Dan
2010-11-25 19:59         ` Bernt Hansen
2010-11-25 21:00           ` [OT] retrieving old messages [WAS] " Dan Davison
2010-11-26  0:19             ` [OT] retrieving old messages Bernt Hansen
2010-11-29  2:34             ` [OT] retrieving old messages [WAS] Re: [Babel] Handling of errors when using Ledger Matt Lundin
2010-11-29  9:14               ` [OT] retrieving old messages Sébastien Vauban
2010-11-29 14:11                 ` Matt Lundin
2010-11-25 21:13           ` [Babel] Handling of errors when using Ledger Sébastien Vauban
2010-11-25 20:03         ` Sébastien Vauban
2010-11-26  8:34         ` Eric S Fraga
2010-11-26 11:47           ` Dan Davison
2010-11-26 12:39             ` Eric S Fraga
2010-12-23 10:28               ` Dan Davison
2010-12-23 15:52                 ` Sébastien Vauban
2010-12-23 19:07                 ` Eric S Fraga
2011-03-05  0:29                   ` Dan Davison
2011-03-07  9:11                     ` Eric S Fraga
2010-11-27 22:04             ` [Babel] Piping between code blocks Was: " Eric Schulte

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=87mxqiv7q3.wl%ucecesf@ucl.ac.uk \
    --to=ucecesf@ucl.ac.uk \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \
    /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).