From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Alsinet Subject: Re: [Proposal] Source Blocks with Post-Extensions Date: Fri, 26 Jul 2019 10:52:42 -0500 Message-ID: References: <87a7d10zss.fsf@gmail.com> <877e8425ap.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000004551f058e97899a" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40173) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hr2Wf-0006rQ-27 for emacs-orgmode@gnu.org; Fri, 26 Jul 2019 11:52:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hr2Wc-0007Ei-PY for emacs-orgmode@gnu.org; Fri, 26 Jul 2019 11:52:55 -0400 Received: from mail-ot1-f51.google.com ([209.85.210.51]:38181) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hr2Wc-0007CV-GB for emacs-orgmode@gnu.org; Fri, 26 Jul 2019 11:52:54 -0400 Received: by mail-ot1-f51.google.com with SMTP id d17so55846537oth.5 for ; Fri, 26 Jul 2019 08:52:54 -0700 (PDT) In-Reply-To: <877e8425ap.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Ken Mankoff Cc: Dmitrii Korobeinikov , emacs-orgmode , "Berry, Charles" --00000000000004551f058e97899a Content-Type: text/plain; charset="UTF-8" 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 wrote: > > On 2019-07-26 at 08:58 -04, Martin Alsinet > 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. > --00000000000004551f058e97899a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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<= br> > 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.

=C2=A0 -k.
--00000000000004551f058e97899a--