On Tue, Jul 10, 2012 at 10:19 AM, Thomas S. Dye wrote:
> John Hendy writes:
>
>> On Mon, Jul 9, 2012 at 7:35 PM, Thomas S. Dye wrote:
>>> John Hendy writes:
>>>
I have typically outputted graphics from R via tikzDevice manually,
but gave my first whirl to just including things via the
John Hendy writes:
> On Mon, Jul 9, 2012 at 7:35 PM, Thomas S. Dye wrote:
>> John Hendy writes:
>>
>>> I have typically outputted graphics from R via tikzDevice manually,
>>> but gave my first whirl to just including things via the :file
>>> argument in my block header. In the process, I was tr
On Mon, Jul 9, 2012 at 7:35 PM, Thomas S. Dye wrote:
> John Hendy writes:
>
>> I have typically outputted graphics from R via tikzDevice manually,
>> but gave my first whirl to just including things via the :file
>> argument in my block header. In the process, I was trying to get this
>> to work
John Hendy writes:
> I have typically outputted graphics from R via tikzDevice manually,
> but gave my first whirl to just including things via the :file
> argument in my block header. In the process, I was trying to get this
> to work and found I needed to use:
>
> -
> :results output graphi
I have typically outputted graphics from R via tikzDevice manually,
but gave my first whirl to just including things via the :file
argument in my block header. In the process, I was trying to get this
to work and found I needed to use:
-
:results output graphics
-
This is listed on Worg o
