emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Redirecting stderr to stdout with babel/shell
Date: Wed, 21 Jan 2015 17:52:46 +0100	[thread overview]
Message-ID: <2015-01-21T17-51-21@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87h9vxw3ej.fsf@Rainer.invalid

* Achim Gratz <Stromeko@nexgo.de> wrote:
> Karl Voit writes:
>> However with an additional "echo" at the end:
>
> You need to understand what you're doing or at least copy the code
> exactly.  The last line in my example is a colon ":" so that the shell
> exit code is always zero.  

You're right. The only thing I did not know was the meaning of the
colon.

http://stackoverflow.com/a/3224910 did fix my ignorance :-)

> If not, Babel will ignore the output since it interprets any
> non-zero exit code as failure.  Since you've redirected STDERR to
> STDOUT the error buffer that would normally let you know what
> happened stays empty.  The echo has the same effect, but produces
> a blank line you don't want.

Yes, now everything makes sense to me. Thanks for your pointer!

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

next prev parent reply	other threads:[~2015-01-21 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 16:27 Redirecting stderr to stdout with babel/shell Karl Voit
2015-01-01 17:10 ` Michael Brand
2015-01-02 21:43 ` Samuel Wales
2015-01-04 14:07   ` John Kitchin
2015-01-11 10:54     ` Karl Voit
2015-01-11 16:44       ` John Kitchin
2015-01-11 18:31         ` Karl Voit
2015-01-11 18:58           ` Achim Gratz
2015-01-21 16:52             ` Karl Voit [this message]
2015-01-11 11:43 ` Achim Gratz
2015-01-11 15:02   ` Karl Voit

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=2015-01-21T17-51-21@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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

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).