[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] babel, header arguments.
From: |
Thomas S. Dye |
Subject: |
Re: [O] babel, header arguments. |
Date: |
Fri, 21 Nov 2014 10:36:33 -1000 |
address@hidden (jenia.ivlev) writes:
> address@hidden (Thomas S. Dye) writes:
>
>> Aloha,
>>
>> address@hidden (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
- [O] babel, header arguments., jenia.ivlev, 2014/11/18
- Re: [O] babel, header arguments., Sebastien Vauban, 2014/11/20
- Re: [O] babel, header arguments., jenia.ivlev, 2014/11/21
- Re: [O] babel, header arguments., Thomas S. Dye, 2014/11/21
- Re: [O] babel, header arguments., jenia.ivlev, 2014/11/21
- Re: [O] babel, header arguments., jenia.ivlev, 2014/11/21
- Re: [O] babel, header arguments.,
Thomas S. Dye <=
- Re: [O] babel, header arguments., jenia.ivlev, 2014/11/21