Ista Zahn wrote:
options(width=n) is supposed to work, and does for me. I don't use Lyx
though...
-Ista
On Tue, Nov 10, 2009 at 4:27 PM, Mark Connolly
wrote:
I am not really sure where in the interactions this is handled, but I
would
like to keep echo-ed R code chunks from running pas
Mark Connolly wrote:
Thanks. I guess it kind of works for me as well. The contents of a
dataframe will display in the specified width, but doing a
str(dataframe) will happily run past the width set in options and use up
the device width (command line). I guess this may be my issue.
Options
Thanks. I guess it kind of works for me as well. The contents of a
dataframe will display in the specified width, but doing a
str(dataframe) will happily run past the width set in options and use up
the device width (command line). I guess this may be my issue.
Options(width) does work for
Ista Zahn wrote:
>
> options(width=n) is supposed to work, and does for me. I don't use Lyx
> though...
>
> -Ista
> On Tue, Nov 10, 2009 at 4:27 PM, Mark Connolly
> wrote:
>> I am not really sure where in the interactions this is handled, but I
>> would
>> like to keep echo-ed R code chunks f
options(width=n) is supposed to work, and does for me. I don't use Lyx though...
-Ista
On Tue, Nov 10, 2009 at 4:27 PM, Mark Connolly wrote:
> I am not really sure where in the interactions this is handled, but I would
> like to keep echo-ed R code chunks from running past the right margin and
>
I am not really sure where in the interactions this is handled, but I
would like to keep echo-ed R code chunks from running past the right
margin and off the page. I started with R and options(width=n), but
this does not seem to do anything (in the context of a document -- line
command works j
6 matches
Mail list logo
