On Tue, Jun 19, 2012 at 7:55 AM, suvayu ali wrote:
> Hi Tom,
>
> On Mon, Jun 18, 2012 at 9:05 PM, Thomas S. Dye wrote:
>>
>> The :noweb header argument can take several values to control when these
>> noweb references are expanded. Many of these don't show in the Org-mode
>> manual on Worg. Her
Hi Tom,
On Mon, Jun 18, 2012 at 9:05 PM, Thomas S. Dye wrote:
>
> The :noweb header argument can take several values to control when these
> noweb references are expanded. Many of these don't show in the Org-mode
> manual on Worg. Here they are in org.texi:
[...]
I had missed these options!
suvayu ali writes:
> Hi Thomas,
>
> On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
>> #+CALL: clean-up() :exports none
>>
>> This way, the original code block will be exported and subsequent calls
>> should not be.
>
> I think John's use case requires other code blocks "using" the common
John Hendy writes:
> On Mon, Jun 18, 2012 at 12:16 PM, suvayu ali
> wrote:
>> Hi Thomas,
>>
>> On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
>>> #+CALL: clean-up() :exports none
>>>
>>> This way, the original code block will be exported and subsequent calls
>>> should not be.
>>
>> I th
> On Mon, Jun 18, 2012 at 6:50 PM, John Hendy wrote:
> > #+name: preamble
> > #+begin_src R :exports none
> > tikzDevice("file-name")
> > #+end_src
>
> Are you trying to use "file-name" as a variable? if so I think the
> source block header should include this: ":var file-name" and the source
> b
On Mon, Jun 18, 2012 at 12:16 PM, suvayu ali
wrote:
> Hi Thomas,
>
> On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
>> #+CALL: clean-up() :exports none
>>
>> This way, the original code block will be exported and subsequent calls
>> should not be.
>
> I think John's use case requires other
Hi Thomas,
On Mon, Jun 18, 2012 at 7:11 PM, Thomas S. Dye wrote:
> #+CALL: clean-up() :exports none
>
> This way, the original code block will be exported and subsequent calls
> should not be.
I think John's use case requires other code blocks "using" the common
code block. Can a "CALL" be done
John Hendy writes:
> I recently started a paper using Babel in a more full-functioned way
> to display both R code as well as output. Previously I've just used
> the convenience of headings and src blocks to create R plots and have
> the code stored nicely for future reference. I'm exporting via
Hi John,
My R knowledge is zero, but I'll give it a shot.
On Mon, Jun 18, 2012 at 6:50 PM, John Hendy wrote:
> #+name: preamble
> #+begin_src R :exports none
> tikzDevice("file-name")
> #+end_src
>
Are you trying to use "file-name" as a variable? if so I think the
source block header should inc
On Mon, Jun 18, 2012 at 11:08 AM, suvayu ali
wrote:
> Hi John,
>
> On Mon, Jun 18, 2012 at 4:53 PM, John Hendy wrote:
>> Doing this got me to thinking how it would be
>> quite neat to run code in a block but mark it to be omitted from
>> export for these kind of "setup" lines that are necessary f
Hi John,
On Mon, Jun 18, 2012 at 4:53 PM, John Hendy wrote:
> Doing this got me to thinking how it would be
> quite neat to run code in a block but mark it to be omitted from
> export for these kind of "setup" lines that are necessary for the
> desired graphs but unnecessary for your reader to se
I recently started a paper using Babel in a more full-functioned way
to display both R code as well as output. Previously I've just used
the convenience of headings and src blocks to create R plots and have
the code stored nicely for future reference. I'm exporting via LaTeX
to create something to
12 matches
Mail list logo
