From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel] No output returned if just one command is failing
Date: Wed, 01 Dec 2010 07:29:10 -0700 [thread overview]
Message-ID: <87r5e1ftxl.fsf@gmail.com> (raw)
In-Reply-To: <80eia1ondv.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Wed, 01 Dec 2010 10:25:48 +0100")
Hi Seb,
I don't forsee adding partial results insertion both because
- it would add a good deal of complexity to the code to insert results
part-way through a run
- the current behavior of only inserting results on a fully successful
run is reasonable and is probably more obvious (at least to me) than
inserting partial results
Best -- Eric
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> #+TITLE: Babel doesn't return output if one command fails
> #+DATE: 2010-12-01
> #+LANGUAGE: en_US
>
> * Abstract
>
> When just one command fails in Babel, then there is no shell output at all.
>
> * One command fails
>
> For example, the last command (=datee=) is not found:
>
> #+begin_src sh :var file=(buffer-file-name) :results output :exports both
> echo $(basename $file)
> datee
> #+end_src
>
> #+results:
>
> Result set is empty, while the =echo= command did work, and did produce
> output.
>
> * All commands are successful
>
> Only if all commands are successful, I see all results:
>
> #+begin_src sh :var file=(buffer-file-name) :results output :exports both
> echo $(basename $file)
> date
> #+end_src
>
> #+results:
> #+begin_example
> ecm-babel-one-error-no-results.txt
> Wed, Dec 01, 2010 10:21:09 AM
> #+end_example
>
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-12-01 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 9:25 [Babel] No output returned if just one command is failing Sébastien Vauban
2010-12-01 14:29 ` Eric Schulte [this message]
2010-12-01 15:25 ` Sébastien Vauban
2010-12-02 10:03 ` Sébastien Vauban
2010-12-02 13:10 ` Dan Davison
2010-12-02 14:35 ` Eric Schulte
2010-12-02 20:34 ` Sébastien Vauban
2010-12-02 15:43 ` Sébastien Vauban
2010-12-02 18:02 ` Dan Davison
2010-12-02 20:27 ` Sébastien Vauban
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5e1ftxl.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.