similar to: 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. > This could be related to >

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 regards, Sebastian Am 15.05.20 um 03:50 schrieb William Dunlap via R-devel: > Is it just

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. So, thank you to the bug-fixers... :) On Sat, May 16, 2020 at 2:54 AM Duncan

> On Friday, May 15, 2020, 12:13:04 PM EDT, Dirk Eddelbuettel <edd at debian.org> wrote: > On 15 May 2020 at 15:41, Martin Maechler wrote: > | <whining> > | > |??? 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

On 15/05/2020 9:41 a.m., Martin Maechler wrote: [ deletions ] > <whining> > > 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? > > Notably a highly

On 15 May 2020 at 15:41, Martin Maechler wrote: | <whining> | | 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? | | Notably a highly staffed enterprise such as Rstudio (viz the bug

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.r-project.org was littered with out-of-date information, but it seems that Simon has now cleaned

MM> but I don't think we'd want to MM> change all.equal.language() at this point in time Although it would be nice if all.equal looked at least at attributes of formulas so we did not get results like > form <- y ~ x1 %in% x2 > all.equal(form, terms(form)) [1] TRUE > all.equal(terms(y~x1+x2+Error(x3/x2), specials="Error"), terms(y~x1+x2+Error(x3/x2)))

On 12/10/2015 9:51 AM, Ben Bolker wrote: > Duncan Murdoch <murdoch.duncan <at> gmail.com> writes: > > BB> >>>> It seems odd/inconvenient to me that the "ignore.environment" argument >>>> of identical() only applies to closures (which I read as 'functions' -- >>>> someone can enlighten me about the technical differences

I noticed the following file descriptor leak when I couldn't remove a package unless I shut down the R session that had loaded and used it. The function that triggered the problem printed the output of a call to parse(). Each time one prints a srcref a connection is opened and not closed. It looks like it happens in as.character.srcref's call to getSrcLines, which has some logic I

Hello everybody, this might be a trivial question, but I have been unable to find this using Google. I am trying to replace double backslashes with single backslashes using gsub. There seems to be some unexpected behaviour with regards to the replacement string "\\". The following example uses the string C:\\ which should be converted to C:\ . > gsub("\\\\",

The following code works, to gsub single quotes to double quotes: line <- gsub("'", '"', line) (that's a single quote within doubles then a double within singles if your viewer's font is not good). But The R Language Manual tells me that Quotes and other special characters within strings are specified using escape sequences: \' single quote \"

I suspect that the parser used it to store comments, including the initial "#", before R started using the srcref attribute. (S also stored comments in the parse tree.) Bill Dunlap TIBCO Software wdunlap tibco.com On Tue, Nov 12, 2019 at 4:16 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 12/11/2019 5:01 p.m., William Dunlap via R-devel wrote: > > In

I am trying to check for backslashes in data, then remove them when I find them, but am having a difficult time figuring out the best way to do it. I know the backslash is the escape character in R, and I should be able to use 'gsub' to accomplish this, but I all I seem to be getting are errors. For example: If entry is: "Hello\World" I want: "HelloWorld"

Dear helpers, I'm trying to replace a character with a unicode code inside a data frame using gsub(), but unsuccessfully. > data.frame(animals=c("dog","wolf","cat"))->my.data > gsub("o","\u0254",my.data$animals)->my.data$animals > my.data$animals [1] "d??g" "w??lf" "cat" It's not that a data

I have a path: path = "/nfs/users/nfs_n/ns9/ Phenotype Analysis/Results/Run_AmplRatio_neg BinaryAll trained without akapn+tnik.csv" I wish to replace the spaces with "\ " so that it can be read by a system call to unix. Using gsub I try: > gsub(" ","\\ ",path) [1] "/nfs/users/nfs_n/ns9/Phenotype Analysis/Results/Run_AmplRatio_neg BinaryAll

Hi, all. I didn't find something like this in the faq list: I wound like build a function to substitute single backslashes in a string to double: ChangeSlash<-function(dir) ... so ChangeSlash("C:\mydocs\test") returns "C:\\mydocs\\test" Thanks, C. _______________________________________________________ Abra sua conta no Yahoo! Mail: 1GB de espa?o, alertas

Hi, all. I've been searching google, bug reports and forums and have looked in all the asterisk-users list archives back to 2003 but haven't seen an answer to this, so thought I'd post here. The problem seems to be that Asterisk 1.6.0.5 is sending backslashes (needed to escape commas and so forth in 1.4.21.2) as *literal* backslashes to Mysql, so that Mysql gives a syntax error

Hi, I would really like to have a way to split long string literals across multiple lines in R. Currently, if a string literal spans multiple lines, there is no way to inhibit the introduction of newline characters: > "aaa + bbb" [1] "aaa\nbbb" If a line ends with a backslash, it is just ignored: > "aaa\ + bbb" [1] "aaa\nbbb" We could use

I find that Sys.glob() doesn't like UNC paths where the initial slashes are backslashes. The help page for Sys.glob() doesn't specificly mention UNC paths, but does say: "File paths in Windows are interpreted with separator \ or /." Is the failure to treat a path beginning with a double-backslash as a UNC network drive path the intended behavior? E.g., on a Windows system