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

From: Eric Schulte <eric.schulte@gmx.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BABEL] Redirect stderr to stdout?
Date: Fri, 02 Mar 2012 13:23:09 -0700	[thread overview]
Message-ID: <87booelpew.fsf@gmx.com> (raw)
In-Reply-To: 20120302194714.GB27465@kenny.local

Viktor Rosenfeld <listuser36@googlemail.com> writes:

> Hi Eric,
>
> Eric Schulte wrote:
>
>> Currently the only action Babel takes with STDERR is to display it in a
>> pop-up buffer when code block evaluation fails.  
>
> On my system (OS X) the buffer does not popup. I just tried
>
> #+BEGIN_SRC sh
> echo foo 1>&2
> #+END_SRC
>

That is because the evaluation did not fail, try

#+BEGIN_SRC sh
echo foo 1>&2
exit 1
#+END_SRC

>
> in Aquamacs and Cocoa Emacs. Strangely, the output seems to be lost
> entirely.

I don't pretend to understand the many oddities of Aquamacs, and I don't
know what Cocoa Emacs is.

> Normally, stderr is captured in another buffer which I have to open
> manually.
>
>> It would certainly be
>> possible to add :results header argument to incorporate STDERR into
>> results (and this desire has been expressed previously).  Reasonable
>> combination options would likely include (at least) the following.
>> 
>> | stderr-only | return stderr instead of stdout    |
>> | 2>&1        | interleave stderr and stdout       |
>> | concat      | add stderr to the end of stdout    |
>> | list        | return a list of stderr and stdotu |
>> 
>> The best (read simple and extensible) implementation and syntax for this
>> behavior is not obvious to me (and I simply don't have time).  If you
>> (or anyone on the list) have any interest in hacking elisp code the
>> place to start would be `org-babel-eval' for a serious implementation,
>> or an quick hack may be possible through customization of the
>> `org-babel-eval-error-notify' function.
>> 
>> Hope this helps.
>
> Okay, thanks. My elisp skills are very rudimentary and this is beyond
> me. Maybe somebody else will pick it up if the interest is big enough.
>

This feature has been requested previously on the mailing list, so there
is certainly demand.  As always demand outstrips development resources.

Best,

>
> Cheers,
> Viktor
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

next prev parent reply	other threads:[~2012-03-02 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 11:29 [BABEL] Redirect stderr to stdout? Viktor Rosenfeld
2012-03-02 16:21 ` Eric Schulte
2012-03-02 19:47   ` Viktor Rosenfeld
2012-03-02 20:23     ` Eric Schulte [this message]
2012-03-03 15:52       ` Viktor Rosenfeld

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=87booelpew.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.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

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