similar to: Write unix format files on windows and vice versa

Dear R developers, I am developing an R package which returns strings with new line codes. I am not sure if I should use "\r\n" or "\n" in my returned strings on Windows platforms. What is the recommended best practice for package developers (and code in base R) for coding new lines in strings? And just out of curiosity: What is the reason (or history) for preferring

Hi List, When doing 'ael reload' on two servers, which are setup with asterisk 1.4.22 and 1.4.35 respectively, I am getting multiple lines of this strange error: ERROR[15483]: ael.flex:647 ael_yylex: Unhandled char(s): On three other servers with same versions of asterisk, i.e. 1.4.22, I don't see this error. Number of lines of the error are the same as the number of lines of the

This patchset attempts to address a number of shortcomings in the firstboot infrastructure I came across while working with v2v conversion of various Windows VMs. Roman Kagan (4): firstboot: consolidate line ending conversion firstboot: enhance firstboot driver script for Windows firstboot: make script naming descriptive convert_windows: split firstboot into steps

Hi. I've made a strange observation. When having Dovecot (at least) with maildir and moving (via IMAP) mail received by some client (Evolution 3.4) into it the following happens: Regardless of whether the mail was originally(!) set with CRLF or LF (i.e. when I use netcat to submit the plain SMTP to the relaying MTA). When the client (Evolution) had received the mail via POP3 before moving

Gentlefolk, I need to give someone the ability to create Windows-format text documents, which I can then copy (via SMB) to a W2000 machine for further processing. I've got the file-sharing up and running, and Wine installed and running Windows Notepad OK, but I've hit a snag trying to set it up to load Notepad automatically when the file-icon is clicked :- Environment - ubuntu 6.06,

Right, my understanding is that files that specifically need CRLF should say so via .gitattributes somewhere. autocrlf=false ought to work if your Windows editor doesn’t (or can be persuaded not to) introduce CRLFs. I’ve observed that the Visual Studio editor will detect the line-ending style of the file you’re editing, and imitate it. This works great until you create a new file. 😝 So I’ve

Dear all: I am developing a package in R. While I am running R CMD check, I found the following warning message: Found the following C sources/headers with CRLF line endings: src/hem.c src/random4f.h ISO C requires LF line endings. It seems that it comes from a line ending problem in C. What are CRLF/LF line endings? How can I fix it? Thank you for your help in advance. Best, HJ

I do have full access to that directory. I have the bbHist package in c:/PROGRA~1/R/rw2011/library/bbHist directory. Then under the library directory I did check and build. Here's what I got: $ R CMD check bbHist * checking for working latex ... OK * using log directory 'c:/progra~1/r/rw2011/library/bbHist.Rcheck' * using R version 2.1.1, 2005-06-20 * checking for file

Dear R People: I have a small function that solves the "Jumble" puzzle from the newspaper (I know...big deal). It uses the the Linux "words" file. My question is: is there a similar words file for Windows, please? Thanks, Happy New (Gnu) Year. Sincerely, Erin -- Erin Hodgess Associate Professor Department of Computer and Mathematical Sciences University of Houston -

Recent functionality in jsonlite allows for streaming json to a user supplied connection object, such as a file, pipe or socket. RFC7159 prescribes json must be encoded as unicode; ISO-8859 (including latin1) is invalid. Hence I would like R to write strings as utf8, irrespective of the type of connection, platform or locale. Implementing this turns out to be unsurprisingly difficult on windows.

I am trying someone's example to build a R package, but I get some errors, Can someone help me to figure it out? thanks, * using log directory '/home/aiminy/myrpackages/roots.Rcheck' * using R version 2.6.1 (2007-11-26) * checking for file 'roots/DESCRIPTION' ... OK * this is package 'roots' version '0.1-1' * checking package dependencies ... OK * checking if

I've been using the mono-repo [ http://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo] and this morning I ran into an issue where I am unable to submit using the mono repo. I traced this down to the fact that many files explicitly have the property svn:eol-style set to native. On the git side, we have core.autocrlf=false, which means that git will checkout

On 19.3.2013 19:13, LRN wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 19.03.2013 20:35, Janne Hyv?rinen wrote: >> On 19.3.2013 15:49, JonY wrote: >>> On 3/19/2013 19:59, Janne Hyv?rinen wrote: >>>> On 18.3.2013 12:25, Erik de Castro Lopo wrote: >>>>> JonY wrote: >>>>> >>>>>> Before anyone does

Hello All, R 2.11.1 Windows XP, 32-bit Help says that default is eol=''\n''. To me, that represents Linefeed (LF) >From Help: eol the character(s) to print at the end of each line (row). For example, eol="\r\n" will produce Windows'' line endings on a Unix-alike OS, and eol="\r" will produce files as expected by Mac OS Excel 2004. I would

I moved my own llvm tree out of the way and tried to get a fresh copy from cvs and build everything from scratch... and it worked! apart from one little problem, a file was moved and should be removed from the project files -- here is a patch. There is a small problem with submitting patches for the .vcproj files - VS saves them with CRLF line endings but the CVS versions appear to have only

http://bugzilla.mindrot.org/show_bug.cgi?id=1157 Summary: ssh-keygen doesn't handle DOS line breaks Product: Portable OpenSSH Version: 3.8.1p1 Platform: All URL: http://openssh.org/txt/draft-ietf-secsh-publickeyfile- 02.txt OS/Version: All Status: NEW Severity: normal

Hi everybody! I hope that you are not already "pissed off" of all the crlf/lf conversion discussion between dos and unix ;-) Concerning that topic I have a question / suggestion: This is what we have: We are using a Win NT 4.0 Server with Win95 clients. Additionally we have a Sun (Solaris 2.5) running in the same network. To access the Sun in character mode we use a terminal

Dear all, When running R CMD check on Windows XP to test my package I get the following warning message: "* checking line endings in C/C++/Fortran sources/headers ... WARNING Found the following sources/headers with CR or CRLF line endings: src/xpsDict.h" The problem is that this file is created by the compiler AUTOMATICALLY during the compilation process, and since the file is

Tony Plate wrote: > ligges@statistik.uni-dortmund.de wrote: > >> tplate@blackmesacapital.com wrote: >> >> >>> I've noticed that seek(con, 0, "end", rw="r") on a file connection >>> does not always work correctly after a write (R 2.1.0 on Windows). >>> >>> [Is a call to fflush() needed inside file_seek() in

Hi, While running R CMD build on one of the Bioc packages, I'm getting the following error message * creating vignettes ... OK * cleaning src * removing junk files * checking for LF line-endings in source files Can't call method "print" on an undefined value at /home/sfalcon/arch/x86_64/R-2.3/bin/build line 646. The pacakge has CRLF line endings in source files. >