Hi all
On Mon, May 13, 2013 at 7:59 PM, Achim Gratz strom...@nexgo.de wrote:
All things considered, there may be room for an argument that Babel
shouldn't ignore the data from STDOUT on non-zero exit [...]
Yes please, and a report of the actual exit status in the babel result
would be nice,
http://thread.gmane.org/gmane.emacs.orgmode/45828/focus=45881
Sorry, the above was with the wrong message focus. Corrected:
http://thread.gmane.org/gmane.emacs.orgmode/45828/focus=46415
Hi,
in the following org file the second block gets not exported (tested with
text and html exporter, release_8.0.2-119-g646f1a):
--8---cut here---start-8---
#+OPTIONS: toc:nil author:nil
#+BEGIN_SRC sh :exports results :results output
cat testdiff.txt.orig
Why is the `diff' command alone not exported while the piped `diff' via
`cat' works? Is this this a bug?
Figured out myself, sorry for the noise. It has to do with the exit
status of the `diff', which is 1 if the files are different. So I use
the pipe through `cat'.
Oliver Večerník ov at vecernik.at writes:
Why is the `diff' command alone not exported while the piped `diff' via
`cat' works?
The exit code is not zero since diff found differences, so Babel assumes the
script produced an error. Try this instead when you don't know what the
return code of the
Oliver Večerník ov at vecernik.at writes:
Figured out myself, sorry for the noise. It has to do with the exit
status of the `diff', which is 1 if the files are different. So I use
the pipe through `cat'.
Useless use of cat...
Regards,
Achim
Figured out myself, sorry for the noise. It has to do with the exit
status of the `diff', which is 1 if the files are different. So I use
the pipe through `cat'.
Useless use of cat...
At least the return status is zero. But I agree with you, a colon is
better here. This is my first use
Achim Gratz writes:
Is this this a bug?
I don't think so, although Babel could give a more enlightening message
about why it didn't evaluate STDOUT. It gives this on your original example:
Babel evaluation exited with code 1
Code block produced no output.
All things considered, there may
On 5/13/13, Achim Gratz strom...@nexgo.de wrote:
All things considered, there may be room for an argument that Babel
shouldn't ignore the data from STDOUT on non-zero exit or have an option
to ignore the return code for cases like this.
That sounds good for newcomers.
Samuel
--
The Kafka