I don't like putting it into .Rprofile that much, because I won't be able to share code then - I might put it in scripts where I do this a lot inside a single script, but the situation is more like - many little scripts that have one or maybe two merges inside and it's currently less work to write nomatch=0 than change the option at the top. .Rprofile would've been a decent solution if there wasn't the code sharing constraint.
It's a mess either way, what can I say :) On Fri, May 3, 2013 at 12:23 PM, Arunkumar Srinivasan <[email protected] > wrote: > Eddi, still you can add this line to the top of every R script or even > better directly in the .Rprofile file wherever you run. > > Arun > > On Friday, May 3, 2013 at 5:51 PM, Eduard Antonyan wrote: > > Good point - I might do that, though I'll need to be a bit careful as I > run a lot of scripts on remote computers. > > > On Fri, May 3, 2013 at 10:48 AM, Arunkumar Srinivasan < > [email protected]> wrote: > > Eddi, > > You could just set: options(datatable.nomatch = 0)if you use that > extensively. > > Arun > > > _______________________________________________ > datatable-help mailing list > [email protected] > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/datatable-help > > > >
_______________________________________________ datatable-help mailing list [email protected] https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/datatable-help
