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: Sun, 11 Jan 2015 19:31:00 +0100	[thread overview]
Message-ID: <2015-01-11T19-20-47@devnull.Karl-Voit.at> (raw)
In-Reply-To: m2h9vx1d4c.fsf@gmail.com

* John Kitchin <johnrkitchin@gmail.com> wrote:
> Karl Voit <devnull@Karl-Voit.at> writes:
> Weird. It works for me on MacOSX with bash. Out of curiosity, did you
> try the source: http://kitchingroup.cheme.cmu.edu/org/2015/01/04/Redirecting-stderr-in-org-mode-shell-blocks.org?

I did it now.

What I found out:

echo '#!/usr/bin/zsh
/usr/bin/zsh $1
} 2>&1
#end' > ~/src/misc/zsh_stderr_redirected_to_stdout.sh
chmod +x ~/src/misc/zsh_stderr_redirected_to_stdout.sh
cd ~/bin
ln -s ../src/misc/zsh_stderr_redirected_to_stdout.sh .

#+BEGIN_SRC elisp
(setq org-babel-sh-command "~/bin/zsh_stderr_redirected_to_stdout.sh")

... my old script from my previous posting:

#+BEGIN_SRC sh :results output
echo "testing stdout" >&1
echo "testing stderr" >&2
date -g


... with empty additional buffer window. So not happy.

However with an additional "echo" at the end:

#+BEGIN_SRC sh :results output
echo "testing stdout" >&1
echo "testing stderr" >&2
date -g

: testing stdout
: testing stderr
: date: invalid option -- 'g'
: Try `date --help' for more information.

... it works. :-O

Is there an issue with flushing stdout or something?

What is the explanation and the general rule?

Btw, the trick with tangling for writing the script file did not work on my

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

  reply	other threads:[~2015-01-11 18:31 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 [this message]
2015-01-11 18:58           ` Achim Gratz
2015-01-21 16:52             ` Karl Voit
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:

  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-11T19-20-47@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \


* 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


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