Re: [Rd] [External] Re: Testing before release (was: edit() doubles backslashes when keep.source=TRUE)

On Fri, 15 May 2020, Abby Spurdle wrote: This perhaps diverges from the intent of the thread, but... I wanted to say I'm extremely grateful to the people who go the through the bug reports. It's an extremely important job (in the long run, particularly), but perhaps not quite as "sexy"-sounding

Re: [Rd] Testing before release (was: edit() doubles backslashes when keep.source=TRUE)

This perhaps diverges from the intent of the thread, but... I wanted to say I'm extremely grateful to the people who go the through the bug reports. It's an extremely important job (in the long run, particularly), but perhaps not quite as "sexy"-sounding as other roles, and probably under-valued.

Re: [Rd] paste(character(0), collapse="", recycle0=FALSE) should be ""

There is still the situation where **both** 'sep' and 'collapse' are specified: > paste(integer(0), "nth", sep="", collapse=",") [1] "nth" In that case 'recycle0' should **not** be ignored i.e. paste(integer(0), "nth", sep="", collapse=",", recycle0=TRUE) should return the empty string

Re: [Rd] paste(character(0), collapse="", recycle0=FALSE) should be ""

Hi all, This makes sense to me, but I would think that recycle0 and collapse should actually be incompatible and paste should throw an error if recycle0 were TRUE and collapse were declared in the same call. I don't think the value of recycle0 should be silently ignored if it is actively specified

Re: [Rd] paste(character(0), collapse="", recycle0=FALSE) should be ""

Totally agree with that. H. On 5/15/20 10:34, William Dunlap via R-devel wrote: I agree: paste(collapse="something", ...) should always return a single character string, regardless of the value of recycle0. This would be similar to when there are no non-NULL arguments to paste; collapse="." gi

Re: [Rd] paste(character(0), collapse="", recycle0=FALSE) should be ""

I agree: paste(collapse="something", ...) should always return a single character string, regardless of the value of recycle0. This would be similar to when there are no non-NULL arguments to paste; collapse="." gives a single empty string and collapse=NULL gives a zero long character vector. > pa

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

To discuss this further, we should probably move over to R-sig-mac and change the subject header. -pd > On 15 May 2020, at 19:26 , peter dalgaard wrote: > > Actually, it's not that hard to set up for a source compile for MacOS. -- Peter Dalgaard, Professor, Center for Statistics, Copenha

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

Actually, it's not that hard to set up for a source compile for MacOS. The hard part is to do it precisely like the CRAN binaries so that you can run binary packages off CRAN, but in other setups you can just build packages from source. A stone in the shoe has been that the documentation on mac

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

I build windows binaries from source. As of now, the only choice is R-revel unless I want to monkey around more with Jeroens’s PKGBUILD script (which is On my to-do list). It’s pretty straightforward, although I’m seeing a lot of issues with packages which had explicit calls to LOCALSOFT in config

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

Nightly binary builds of R-devel for macOS are available: http://mac.r-project.org ~~~ Kylie Ariel Bemis (she/her) Khoury College of Computer Sciences Northeastern University kuwisdelu.github.io On May 15, 2020, at 12:48 PM, brodie gaslam via R-devel mailto

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

> On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel > wrote: > On 15 May 2020 at 15:41, Martin Maechler wrote: > | > | > |    Why does nobody anymore  help R development by working with > |    "R-devel", or at least then the alpha, beta and the "RC" > |    (Release Candidate) version

[Rd] ftable <-> data.frame etc {was "justify hard coded in format.ftable"}

> Gabor Grothendieck > on Thu, 14 May 2020 06:56:06 -0400 writes: > If you are looking at ftable could you also consider adding > a way to convert an ftable into a usable data.frame such as > the ftable2df function defined here: > https://stackoverflow.com/questions/11141406/reshapin

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

On 15 May 2020 at 15:41, Martin Maechler wrote: | | | Why does nobody anymore help R development by working with | "R-devel", or at least then the alpha, beta and the "RC" | (Release Candidate) versions that we release daily for about one | month before the final release? | |

Re: [Rd] Daily News about R-devel/NEWS is not updating

Thank you! Jen On Fri, May 15, 2020 at 9:02 AM Duncan Murdoch wrote: > On 15/05/2020 10:39 a.m., Jennifer Lyon wrote: > > Hi: > > > > The "Daily News about R-devel/NEWS" webpage at > > http://developer.r-project.org/blosxom.cgi/R-devel/NEWS seems to not be > > updating. As of today, the latest

Re: [Rd] Daily News about R-devel/NEWS is not updating

On 15/05/2020 10:39 a.m., Jennifer Lyon wrote: Hi: The "Daily News about R-devel/NEWS" webpage at http://developer.r-project.org/blosxom.cgi/R-devel/NEWS seems to not be updating. As of today, the latest entry is Tue, 14 Apr 2020. Thanks. Thanks for noticing that. It's now fixed. (The issu

[Rd] Testing before release (was: edit() doubles backslashes when keep.source=TRUE)

On 15/05/2020 9:41 a.m., Martin Maechler wrote: [ deletions ] Why does nobody anymore help R development by working with "R-devel", or at least then the alpha, beta and the "RC" (Release Candidate) versions that we release daily for about one month before the final release?

[Rd] Daily News about R-devel/NEWS is not updating

Hi: The "Daily News about R-devel/NEWS" webpage at http://developer.r-project.org/blosxom.cgi/R-devel/NEWS seems to not be updating. As of today, the latest entry is Tue, 14 Apr 2020. Thanks. Jen [[alternative HTML version deleted]] __ R-deve

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

> Sebastian Meyer > on Fri, 15 May 2020 10:47:55 +0200 writes: > I can confirm this changed behaviour. I just compared R-3.6.3 with > yesterday's R-devel. Using R-devel, the tempfile opened by the editor > (Emacs for me, but shouldn't matter) contains doubled backslashes.

Re: [Rd] justify hard coded in format.ftable

Thanks for the links. I agree that such a feature would be a nice addition, and could make ftable even more useful. In the same spirit, I think it could be useful to mention the undocumented base::as.data.frame.matrix function in documentation of table and xtabs (in addition to the already ment

Re: [Rd] justify hard coded in format.ftable

If you are looking at ftable could you also consider adding a way to convert an ftable into a usable data.frame such as the ftable2df function defined here: https://stackoverflow.com/questions/11141406/reshaping-an-array-to-data-frame/11143126#11143126 and there is an example of using it here:

Re: [Rd] justify hard coded in format.ftable

One can use as.data.frame(as.matrix(tab)) to avoid calling as.data.frame.matrix directly (although I find I do use as.data.frame.matrix anyways sometimes even though it is generally better to call the generic.). Also note that the various as.data.frame methods do not address the examples in the

Re: [Rd] edit() doubles backslashes when keep.source=TRUE

I can confirm this changed behaviour. I just compared R-3.6.3 with yesterday's R-devel. Using R-devel, the tempfile opened by the editor (Emacs for me, but shouldn't matter) contains doubled backslashes. This could be related to https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17800 Best rega