From: tsd@tsdye.com (Thomas S. Dye)
To: "jenia.ivlev" <jenia.ivlev@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: babel, header arguments.
Date: Fri, 21 Nov 2014 10:36:33 -1000 [thread overview]
Message-ID: <m2k32ob8a6.fsf@tsdye.com> (raw)
In-Reply-To: <87bno0iadl.fsf@gmail.com> (jenia ivlev's message of "Fri, 21 Nov 2014 15:09:26 -0500")
jenia.ivlev@gmail.com (jenia.ivlev) writes:
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha,
>>
>> jenia.ivlev@gmail.com (jenia.ivlev) writes:
>>
>>> Also, what if I want to import the actual function defintion into
>>> another src block:
>>>
>>> #+begin_src scheme
>>> (+ (my-plus 3 4) 1)
>>> #+end_src
>>> something here that import the previous function definitions
>>>
>>> Is that possible?
>>
>> Yes, see section 14.10 Noweb reference syntax in the manual.
>>
>> You'll have something that looks like this:
>>
>> #+header: :noweb yes
>> #+begin_src scheme
>> <<previous-function-definition>>
>> (+ (previous-function 3 4) 1)
>> #+end_src
>>
>> hth,
>> Tom
>
> What do you mean? <<previous-function-definition>> should be replaced
> with the actual function definition? But I use babel-mode so that I can
> interlace code in a natural language document. I want these src blocks
> to be separate.
>
>
Sorry, it refers to the name of the source code block.
,-------------------------------------------------------------------------
| The “noweb” (see <http://www.cs.tufts.edu/~nr/noweb/>) Literate
| Programming system allows named blocks of code to be referenced by using
| the familiar Noweb syntax:
|
| <<code-block-name>>
`-------------------------------------------------------------------------
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-11-21 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 18:44 babel, header arguments jenia.ivlev
2014-11-20 9:36 ` Sebastien Vauban
2014-11-21 19:35 ` jenia.ivlev
2014-11-21 19:49 ` Thomas S. Dye
2014-11-21 20:09 ` jenia.ivlev
2014-11-21 20:32 ` jenia.ivlev
2014-11-21 20:36 ` Thomas S. Dye [this message]
2014-11-21 20:55 ` jenia.ivlev
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=m2k32ob8a6.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jenia.ivlev@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 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).