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 09:21:57 -0700	[thread overview]
Message-ID: <87mx7znfbu.fsf@gmx.com> (raw)
In-Reply-To: <20120302112909.GA25186@kenny.local> (Viktor Rosenfeld's message of "Fri, 2 Mar 2012 12:29:09 +0100")

Viktor Rosenfeld <listuser36@googlemail.com> writes:

> Hi,
>
> is there a way to capture stderr output of a babel block and have it
> appear in the results block (instead of being printed in the *Shell
> Command Output* buffer)? On sh blocks I could redirect myself, but I'm
> trying to capture the output of psql (the PostgreSQL client).
>
> Specifically, I have the following code block:
>
> #+BEGIN_SRC sql :noweb yes :results output verbatim
> \timing on
> <<exp8-test-query>>
> #+END_SRC
>
> #+RESULTS:
> : count
> : 95977
>
> The \timing directive causes psql to print the runtime of the query on
> stderr. If I run the query on the psql command line, the following
> output appears:
>
>  count 
>  -------
>  95977
>  (1 row)
>
>  Time: 1895,558 ms
>
> I suppose that duplicating this output in Babel would be difficult,
> because it interferes with the parsing of the result set.
>

Hi Viktor,

Currently the only action Babel takes with STDERR is to display it in a
pop-up buffer when code block evaluation fails.  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.

Best,

>
> Cheers,
> Viktor
>

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

next prev parent reply	other threads:[~2012-03-02 16:22 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 [this message]
2012-03-02 19:47   ` Viktor Rosenfeld
2012-03-02 20:23     ` Eric Schulte
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=87mx7znfbu.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).