From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: [Babel] No output returned if just one command is failing
Date: Wed, 01 Dec 2010 10:25:48 +0100 [thread overview]
Message-ID: <80eia1ondv.fsf@missioncriticalit.com> (raw)
#+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
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-12-01 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 9:25 Sébastien Vauban [this message]
2010-12-01 14:29 ` [Babel] No output returned if just one command is failing Eric Schulte
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
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=80eia1ondv.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).