From: Marcin Borkowski <mbork@mbork.pl>
To: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: How to call a source code block from another one
Date: Wed, 08 Mar 2017 12:20:08 +0100 [thread overview]
Message-ID: <8737eo582f.fsf@jane> (raw)
Hi all,
and sorry if this is trivial, but I didn't find it in the manual.
Assume that I have a few source code blocks (in my case, in bash) and
I want to call them in sequence. Is it possible to write another,
"master" source code block which would then call those previous blocks?
Best,
--
Marcin Borkowski
next reply other threads:[~2017-03-08 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 11:20 Marcin Borkowski [this message]
2017-03-08 12:21 ` How to call a source code block from another one Rasmus
[not found] <1ed163077135431daf64f84c2bd6ac4b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-08 11:46 ` Eric S Fraga
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=8737eo582f.fsf@jane \
--to=mbork@mbork.pl \
--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).