Re: [Rd] readLines function with R >= 3.5.0

2018-06-19 Thread Michael Lawrence
Hi Jen, Please provide a reproducible example, since the original stack overflow example works in both trunk and patched. Thanks, Michael On Tue, Jun 19, 2018 at 3:45 PM, Jennifer Lyon wrote: > Hi Michael: > > I can confirm Martin's comment. I tested my software with r-devel (r74914) > and it w

Re: [Rd] Bug 16719: kruskal.test documentation for formula

2018-06-19 Thread Thomas Levine
Thomas Levine writes: > I have yet to find any example of my proposed changes causing a > regression. I believe that the most reasonable thing that it might > break is something that depends on either kruskal.test raising an > error or that depends on the specific text in the error message. > > If

Re: [Rd] Bug 16719: kruskal.test documentation for formula

2018-06-19 Thread Thomas Levine
Thomas Levine writes: > I submit a couple options for addressing bug 16719: kruskal.test > documentation for formula. > https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16719 > > disallow-character.diff changes the documentation and error message > to indicate that factors are accepted. > > all

Re: [Rd] readLines function with R >= 3.5.0

2018-06-19 Thread Jennifer Lyon
Hi Michael: I can confirm Martin's comment. I tested my software with r-devel (r74914) and it works, while with r-patched (r74914) it does not work (it hangs, as it did in R 3.5.0). I apologize for it taking so long for me to test this, but is there any chance this fix could make into R 3.5.1? Th

Re: [Rd] aic() component in GLM-family objects

2018-06-19 Thread Suharto Anggono Suharto Anggono via R-devel
In R, family has aic component since version 0.62. There is no aic component in family in R 0.61.3. Looking at blame, https://github.com/wch/r-source/blame/tags/R-0-62/src/library/base/R/family.R , aic component in family is introduced in svn revision 640 (https://github.com/wch/r-source/commi

Re: [Rd] agrep bug

2018-06-19 Thread Kurt Hornik
> Kolter, Andreas writes: > Sorry, I don't understand how to file a bug properly. Nontheless I > want to report this one because it is still in the code after so many > years. Thanks. This is now fixed in the trunk with c74916. Best -k > This bug still exists: > https://stackoverflow.com/