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

Thanks for reporting this, it is a bug, now fixed in R-devel and R-patched (PR#17800). Best Tomas On 5/15/20 3:50 AM, William Dunlap via R-devel wrote: Is it just my installation or does edit() (or fix(), etc.) in R-4.0.0 double all the backslashes when options(keep.source=TRUE)? E.g.,

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,

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

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

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

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)

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] 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] 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

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

Is it just my installation or does edit() (or fix(), etc.) in R-4.0.0 double all the backslashes when options(keep.source=TRUE)? E.g., > options(keep.source=TRUE) > f <- function(x) { cat("\t", x, "\n", sep="") } > edit(f) # exit the editor without making any changes The editor (vi or notepad)