From: Martin Alsinet <martin@alsinet.com.ar>
To: Ken Mankoff <mankoff@gmail.com>
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 10:52:42 -0500 [thread overview]
Message-ID: <CABUJmkCc09yTSOVQn3hqyYtzHdgDTABbQ=3Rv+M4Kig9T3OzDQ@mail.gmail.com> (raw)
In-Reply-To: <877e8425ap.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Well Ken, you improved my workflow right there, I am going to add the
:prologue trick to my shell properties header and get the test error output
in the results block.
Thank you right back!
On Fri, Jul 26, 2019 at 10:18 AM Ken Mankoff <mankoff@gmail.com> wrote:
>
> 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.
>
[-- Attachment #2: Type: text/html, Size: 1623 bytes --]
next prev parent reply other threads:[~2019-07-26 15:52 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
2019-07-26 15:52 ` Martin Alsinet [this message]
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='CABUJmkCc09yTSOVQn3hqyYtzHdgDTABbQ=3Rv+M4Kig9T3OzDQ@mail.gmail.com' \
--to=martin@alsinet.com.ar \
--cc=ccberry@ucsd.edu \
--cc=dim1212k@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
/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).