search for: werbin

...istent with how other arguments typically passed through `plot.default` are handled. I'll be happy to do the patch myself -- I just need to know which thing to patch (the source or the docs). Greg On 2016-08-25 03:00, David Winsemius wrote: >> On Aug 24, 2016, at 5:59 PM, Gregory Werbin >> <greg.werbin at libertymail.net> wrote: >> >> I did a search on Bugzilla for "plot.ts" and didn't find anything on >> this issue. I tried to sign up for Bugzilla to report it, but my >> e-mail address didn't pass your "syntax checkin...

>>>>> Gregory Werbin <greg.werbin at libertymail.net> >>>>> on Thu, 25 Aug 2016 15:21:05 -0400 writes: > I've had a chance to read the source more thoroughly. The chain of > events is as follows: > 1. Local function `plotts()` is defined with argument `cex` that...

I did a search on Bugzilla for "plot.ts" and didn't find anything on this issue. I tried to sign up for Bugzilla to report it, but my e-mail address didn't pass your "syntax checking" for a legal e-mail address. The bug is easily reproducible on my machine as follows: ## start # generate some data y <- arima.sim(list(), 150) # this will definitely dispatch to a

> On Aug 24, 2016, at 5:59 PM, Gregory Werbin <greg.werbin at libertymail.net> wrote: > > I did a search on Bugzilla for "plot.ts" and didn't find anything on this issue. I tried to sign up for Bugzilla to report it, but my e-mail address didn't pass your "syntax checking" for a legal e-mail address. &g...

(Apologies if this is better suited for R-help.) On my system (macOS Sierra, late 2014 MacBook Pro; R 3.4.1, Homebrew build), I found that it is faster to construct a function using eval(call("function", ...)) than using as.function(list(...)). Example: make_fn_1 <- function(a, b) eval(call("function", a, b), env = parent.frame()) make_fn_2 <- function(a, b)