Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

2017-03-03 Thread Henrik Bengtsson
On Fri, Mar 3, 2017 at 9:55 AM, Hadley Wickham wrote: >> But, how you propose a warning-to-error transition should be made >> without wreaking havoc? Just flip the switch in R-devel and see CRAN >> and Bioconductor packages break overnight? Particularly Bioconductor >> devel might become non-fun

Re: [Rd] Trouble installing packages when history mechanism is modified by user profile

2017-03-03 Thread Henrik Bengtsson
Using if (interactive()) utils::loadhistory(file = "~/.Rhistory") should solve your problem. The reason is that install.packages() in turn launches a non-interactive child R process that installs the package. When that process loads your startup file, it fails, because that function can only be

Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

2017-03-03 Thread Hadley Wickham
> But, how you propose a warning-to-error transition should be made > without wreaking havoc? Just flip the switch in R-devel and see CRAN > and Bioconductor packages break overnight? Particularly Bioconductor > devel might become non-functional (since at times it requires > R-devel). For my own

Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

2017-03-03 Thread Henrik Bengtsson
On Fri, Mar 3, 2017 at 9:22 AM, Martin Maechler wrote: >> Henrik Bengtsson >> on Fri, 3 Mar 2017 00:52:16 -0800 writes: > > > I'd like to propose that the whenever the length of condition passed > > to an if or a while statement differs from one, an error is produced > > r

[Rd] Trouble installing packages when history mechanism is modified by user profile

2017-03-03 Thread Hugo Raguet
I tried installing the 'ks' package from my interactive R session, it failed with the following Erreur dans .External2(C_loadhistory, file) : aucun mécanisme d'historique des commandes disponible Calls: Exécution arrêtée second line is french for "no command history mechanism available", fouth

Re: [Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

2017-03-03 Thread Martin Maechler
> Henrik Bengtsson > on Fri, 3 Mar 2017 00:52:16 -0800 writes: > I'd like to propose that the whenever the length of condition passed > to an if or a while statement differs from one, an error is produced > rather than just a warning as today: >> x <- 1:2 >> if (x

Re: [Rd] Bug in nlm()

2017-03-03 Thread Martin Maechler
> Boehnstedt, Marie > on Fri, 3 Mar 2017 10:23:12 + writes: > Dear all, > I have found a bug in nlm() and would like to submit a report on this. > Since nlm() is in the stats-package, which is maintained by the R Core team, bug reports should be submitted to R's Bugzi

[Rd] Bug in nlm()

2017-03-03 Thread Boehnstedt, Marie
Dear all, I have found a bug in nlm() and would like to submit a report on this. Since nlm() is in the stats-package, which is maintained by the R Core team, bug reports should be submitted to R's Bugzilla. However, I'm not a member of Bugzilla. Could anyone be so kind to add me to R's Bugzilla

[Rd] Control statements with condition with greater than one should give error (not just warning) [PATCH]

2017-03-03 Thread Henrik Bengtsson
I'd like to propose that the whenever the length of condition passed to an if or a while statement differs from one, an error is produced rather than just a warning as today: > x <- 1:2 > if (x == 1) message("x == 1") x == 1 Warning message: In if (x == 1) message("x == 1") : the condition has l