From: Ken Mankoff <mankoff@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: No output from babel shell src block
Date: Thu, 12 May 2016 15:36:03 -0400 [thread overview]
Message-ID: <m237pn83x8.fsf@gmail.com> (raw)
In-Reply-To: <CA+M2ft8iyFDdzo7xzrUKQoQMfW0K-s_vXLtZgqwMzmQNtTexnA@mail.gmail.com>
This is a known issue with diff, I think. Add a line containing ":" below, or "echo" or "diff foo bar | cat".
https://stackoverflow.com/questions/27304469/capturing-the-output-of-diff-with-org-babel
I have
(setq org-babel-default-header-args:sh
'((:prologue . "exec 2>&1") (:epilogue . ":"))
)
so that stderr is always displayed in the RESULTS block.
-k.
On 2016-05-12 at 15:24, John Hendy <jw.hendy@gmail.com> wrote:
> Hello,
>
>
> I've not used shell in babel much, and am confused. I was trying to
> include diff output from a block in an analysis and it's not giving
> any output.
>
> As a test, I have a.txt which contains 1 and b.txt which contains 2,
> with boths in ~/Desktop.
>
> Manually:
> $ cd ~/Desktop
> $ diff a.txt b.txt
> 1c1
> < 1
> ---
>> 2
>
> Org:
> #+begin_src shell
>
> cd ~/Desktop
> diff a.txt b.txt
>
> #+end_src
>
> I get "Code block produced no output" with C-c C-c. If I replace the
> diff line with =pwd=, it puts the current directory in the results
> block (works as expected).
>
> I've tried replace, append, output, raw, and value for :results, as
> well as results and both for :exports. I've also tried using a #+name:
> which gives me a results block for the output, but it's empty.
>
> Am I missing something? Perhaps there's an analog for how some
> programs need a print() of some kind for the results to show up? Then
> again, I don't know why =pwd= works... There's no worg page for the
> shell language (surprised me!).
>
>
> Thanks,
> John
next prev parent reply other threads:[~2016-05-12 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 19:24 No output from babel shell src block John Hendy
2016-05-12 19:36 ` Ken Mankoff [this message]
2016-05-12 20:10 ` Thomas S. Dye
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m237pn83x8.fsf@gmail.com \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.