emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Diego Zamboni <diego@zzamboni.org>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: How to intersperse commands with their output in RESULTS block?
Date: Thu, 6 Feb 2020 21:45:19 +0100	[thread overview]
Message-ID: <CAGY83EciGT3hdXAb0bC_nCNYHJN8o5OdLc7Kn4-HDs6zcBqUJg@mail.gmail.com> (raw)
In-Reply-To: <871rr86w8p.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

Hi Eric,

Great idea! I hadn't considered using the =script= command, it's a great
starting point.

Thanks!
--Diego


On Thu, Feb 6, 2020 at 7:55 AM Fraga, Eric <e.fraga@ucl.ac.uk> wrote:

> On Wednesday,  5 Feb 2020 at 18:25, Diego Zamboni wrote:
> > tl;dr: is there a way to have ob-shell (or some similar mode) run
> commands
> > one by one and include the commands, interspersed with their output, in
> the
> > #+RESULTS block?
>
> You haven't said on what type of system but, if Linux, you could try
> using =script= as a starting point:
>
> #+begin_src shell :results output
>   script <<EOF
>   ls
>   echo 'hello'
>   EOF
> #+end_src
>
> You may wish to have a second shell script that massages the output in
> the =typescript= file and ouputs that instead, e.g. to filter the
> carriage returns.
> --
> : Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-233-gc2bc48
>

[-- Attachment #2: Type: text/html, Size: 1325 bytes --]

  reply	other threads:[~2020-02-06 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 17:25 How to intersperse commands with their output in RESULTS block? Diego Zamboni
2020-02-06  6:55 ` Fraga, Eric
2020-02-06 20:45   ` Diego Zamboni [this message]
2020-02-07 15:26     ` Diego Zamboni
2020-02-07 15:49       ` Fraga, Eric
2020-02-07 16:07       ` Adam Porter
2020-02-07 21:30         ` Diego Zamboni
2020-02-08 10:04           ` Fraga, Eric

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=CAGY83EciGT3hdXAb0bC_nCNYHJN8o5OdLc7Kn4-HDs6zcBqUJg@mail.gmail.com \
    --to=diego@zzamboni.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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).