emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <johnrkitchin@gmail.com>
To: Karl Voit <devnull@Karl-Voit.at>
Cc: Karl Voit <news1142@Karl-Voit.at>, emacs-orgmode@gnu.org
Subject: Re: Redirecting stderr to stdout with babel/shell
Date: Sun, 11 Jan 2015 11:44:03 -0500	[thread overview]
Message-ID: <m2h9vx1d4c.fsf@gmail.com> (raw)
In-Reply-To: <2015-01-11T11-53-02@devnull.Karl-Voit.at> (Karl Voit's message of "Sun, 11 Jan 2015 11:54:30 +0100")

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 updated the web page with Achim's  simpler solution.

> * John Kitchin <johnrkitchin@gmail.com> wrote:
>> Check out this solution:
>>
>> http://kitchingroup.cheme.cmu.edu/blog/2015/01/04/Redirecting-stderr-in-org-mode-shell-blocks/
>
> Hm. This does not work on my machine: Debian Wheezy GNU/Linux
>
> Testing the current satus (again):
>
> #+BEGIN_SRC sh :results output
> echo "testing stdout" >&1
> echo "testing stderr" >&2
> date -g
> #+END_SRC
>
> #+RESULTS:
>
> ... no stderr on stdout and date error message in second buffer
>
>
> Creating a wrapper-script similar as described in web-page above:
>
> #+BEGIN_SRC sh
> echo '#!/usr/bin/zsh
> {
> /usr/bin/zsh $1
> } 2>&1' > ~/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 .
> #+END_SRC
>
> #+RESULTS:
>
> Setting the sh-command to this wrapper-script:
>
> #+BEGIN_SRC elisp
> (setq org-babel-sh-command "~/bin/zsh_stderr_redirected_to_stdout.sh")
> #+END_SRC
>
> #+RESULTS:
> : ~/bin/zsh_stderr_redirected_to_stdout.sh
>
> Re-testing status:
>
> #+BEGIN_SRC sh :results output
> echo "testing stdout" >&1
> echo "testing stderr" >&2
> date -g
> #+END_SRC
>
> #+RESULTS:
>
> ... no change except the second buffer for the date error message is
> empty. So it's actually worse than before.
>
>
> Trying with bash (as web-page did):
>
> #+BEGIN_SRC sh
> echo '#!/bin/bash
> {
> /bin/bash $1
> } 2>&1' > ~/src/misc/bash_stderr_redirected_to_stdout.sh
> chmod +x ~/src/misc/bash_stderr_redirected_to_stdout.sh
> cd ~/bin
> ln -s ../src/misc/bash_stderr_redirected_to_stdout.sh .
> #+END_SRC
>
> #+RESULTS:
>
> Setting the sh-command to this wrapper-script:
>
> #+BEGIN_SRC elisp
> (setq org-babel-sh-command "~/bin/bash_stderr_redirected_to_stdout.sh")
> #+END_SRC
>
> #+RESULTS:
> : ~/bin/bash_stderr_redirected_to_stdout.sh
>
> Same result as with zsh :-(
>
>
> Re-setting to standard settings to revoke tests from above:
>
> #+BEGIN_SRC elisp
> (setq org-babel-sh-command "sh")
> #+END_SRC
>
> #+RESULTS:
> : sh
>
> Re-testing status:
>
> #+BEGIN_SRC sh :results output
> echo "testing stdout" >&1
> echo "testing stderr" >&2
> date -g
> #+END_SRC
>
> #+RESULTS:

--
-----------------------------------
John Kitchin
Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu

  reply	other threads:[~2015-01-11 16:44 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 [this message]
2015-01-11 18:31         ` Karl Voit
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:
  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=m2h9vx1d4c.fsf@gmail.com \
    --to=johnrkitchin@gmail.com \
    --cc=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
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).