emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Martin Alsinet <martin@alsinet.com.ar>
Cc: Dmitrii Korobeinikov <dim1212k@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>,
	"Berry, Charles" <ccberry@ucsd.edu>
Subject: Re: [Proposal] Source Blocks with Post-Extensions
Date: Fri, 26 Jul 2019 11:18:06 -0400	[thread overview]
Message-ID: <877e8425ap.fsf@gmail.com> (raw)
In-Reply-To: <CABUJmkBwnF_q7QAmjQW_jxm7z6amNGDT=bufKE600yhyUuozJA@mail.gmail.com>


On 2019-07-26 at 08:58 -04, Martin Alsinet <martin@alsinet.com.ar> wrote...
> I usually have a shell buffer nearby and go there to inspect the
> failed tests when I get no output. The problem is that shell blocks do
> not capture stderr. John Kitchin wrote a blog post
> <http://kitchingroup.cheme.cmu.edu/blog/2015/01/04/Redirecting-stderr-in-org-mode-shell-blocks/>
> about this problem and provided a solution that may work for you, but
> I have not tried it yet.

Ah yes... from my own comments there:

#+begin_src sh :results raw drawer :prologue "exec 2>&1" :epilogue ":"
python -m pytest ./utils
#+end_src

Thanks for reminding me about my past self.

  -k.

  reply	other threads:[~2019-07-26 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  9:00 [Proposal] Source Blocks with Post-Extensions Dmitrii Korobeinikov
2019-04-22 16:51 ` Berry, Charles
2019-04-22 17:15   ` Dmitrii Korobeinikov
2019-04-22 17:31     ` Berry, Charles
2019-04-24 19:05       ` Dmitrii Korobeinikov
2019-06-26 22:09         ` Martin Alsinet
2019-07-03 16:02           ` Dmitrii Korobeinikov
2019-07-26 12:02           ` Ken Mankoff
2019-07-26 12:58             ` Martin Alsinet
2019-07-26 15:18               ` Ken Mankoff [this message]
2019-07-26 15:52                 ` Martin Alsinet
2019-04-22 20:59 ` Tim Cross

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=877e8425ap.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=ccberry@ucsd.edu \
    --cc=dim1212k@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=martin@alsinet.com.ar \
    /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).