emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel opens the error output of a block in a separate window... unless :stdin is given, but how are they connected?
Date: Mon, 07 Sep 2020 06:32:26 +0200	[thread overview]
Message-ID: <877dt6ryud.fsf@gnu.org> (raw)
In-Reply-To: <CA+A2iZYG=jNeBUEez7BT+mhXo5hb_vqE4z1dEMaXpVhT11q9zw@mail.gmail.com> (Vladimir Nikishkin's message of "Tue, 25 Feb 2020 09:36:27 +0800")

Hi Vladimir,

Vladimir Nikishkin <lockywolf@gmail.com> writes:

> #+name: empty
> #+begin_quote
> 1
> #+end_quote
> #+begin_src shell :shebang "#! /usr/bin/chibi-scheme :stdin empty
> (/ 1 0)
> #+end_src

The example above does not work for me.  Can you provide another one?

> Now the chibi-scheme shebang is just an example of an app writing
> things to stderr. The actual content of the <<empty>> doesn't matter,
> the app errs before ever having a chance to read anything from stdin.
> However, when :stdin is given (as in the MWE), the resulting error
> output is printed in the :RESULTS , and if not, it is displayed in a
> separate (a bit annoying) window called "*Org-Babel Error Output*.
> I would like to ask how these two things, stdin, and stderr are
> connected. Perhaps, this is a bug?

I don't know but perhaps you can instrument the relevant functions in
ob-shell.el and see what going on, if you still have this issue?



  reply	other threads:[~2020-09-07  4:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  1:36 org-babel opens the error output of a block in a separate window... unless :stdin is given, but how are they connected? Vladimir Nikishkin
2020-09-07  4:32 ` Bastien [this message]
2020-09-10  8:54   ` Vladimir Nikishkin

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=877dt6ryud.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lockywolf@gmail.com \


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