From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: How to pass a block of text to a code block as data?
Date: Fri, 08 Feb 2013 21:17:32 +0100 [thread overview]
Message-ID: <8638x6y2zn.fsf@somewhere.org> (raw)
In-Reply-To: CA+G3xFiDv=tKo_qOnmMwZC3Cci3hjhMtcugd=z1TC+mEBGWrMA@mail.gmail.com
Hi Michael,
Michael Baum wrote:
> I haven't been able to figure this out from the org-mode documents yet.
> What I would like to do is have a source code block in python or perl or
> something similar. to which I can pass a reference to several lines of text
> that the source code block, when evaluated, would then act on. Which would
> involve iterating through the data text one line at a time and writing the
> output to a buffer.
>
> The text data could be indicated by a specific headline or a named block of
> some sort or maybe an internal link, I'm not particularly fussy just so
> there's a mechanism to do this.
>
> Would appreciate any guidance.
#+name: lines-of-text
: I haven't been able to figure this out from the org-mode documents yet.
: What I would like to do is have a source code block in python or perl or
: something similar. to which I can pass a reference to several lines of text
: that the source code block, when evaluated, would then act on. Which would
: involve iterating through the data text one line at a time and writing the
: output to a buffer.
#+begin_src sh :stdin lines-of-text :results output
grep would
#+end_src
#+results:
#+begin_example
What I would like to do is have a source code block in python or perl or
that the source code block, when evaluated, would then act on. Which would
#+end_example
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-02-08 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 17:06 How to pass a block of text to a code block as data? Michael Baum
2013-02-08 20:17 ` Sebastien Vauban [this message]
2013-02-09 2:59 ` Michael Baum
2013-02-09 18:49 ` Sean O'Halpin
2013-02-11 21:49 ` Michael Baum
2013-02-11 22:07 ` Eric Schulte
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=8638x6y2zn.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 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.