similar to: should dovecot store maildir files with CRLF or LF?

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

I go back and forth between windows and linux, and find myself running into problem with line endings. Is there a way to control the line ending conversion when writing files, such as write and cat? More explicitly I want to be able to write files with LF line endings rather than CRLF line ending on windows; and CRLF line endings instead of LF on linux, and I want to be able to control when the

Hi, could somebody apply the below patch to contrib/cygwin/ssh-host-config? The patch solves a problem with the way, the Windows pendant of the /etc/services file is used. This file has (obviously) CRLF line endings. The ssh-host-config file tries to accomodate that when adding the ssh service entries but I never reviewed this functionality in the light of some major changes in the Cygwin DLL.

On 25/07/2020 4:48 p.m., nospam at altfeld-im.de wrote: > 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

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

No, I don't. But I do know that Samba provides transparent file access -- it has no idea what data is in the files it offers to the clients. It could be a database, a JPEG, a text document, or an executable program. What you suggest would be an extremely bad idea. You need better clients -- it is the clients that interpret the contents of the file. Samba is just another file access method.

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

Hi. I just wondered, the following: My MDA may get mails that use LF or CR/LF end of line encodings and deliver them into maildirs. I couldn't find any information about, whether one should or must convert all into one format, cause AFAIK at least on the IMAP side, CR/LF is always used? How does this work on the maildir/backend side of dovcot? Can it work with both and simply

One of the recent 1.0 commits relating to CRLF handling (maybe 2006-06-24) has changed the behaviour of APPEND when using mbox files with ordinary plain text emails. When a client stores a new message using an APPEND command (eg. saving a draft or copy of a sent message), it uses CRLF consistently as a line-ending throughout the literal data block over the wire - both for the header and the

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

lvqcl wrote: > lvqcl wrote: > > > The patch does the following: > > Does the patch work for linux git? Windows git cannot apply a patch > that was created itself. It looks like that patch was created with the 'git diff' command and hence cannot be applied using the 'git am' command. It does however apply using the patch command. > (It writes LF in

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

https://bugzilla.mindrot.org/show_bug.cgi?id=2287 Bug ID: 2287 Summary: AuthorizedKeysCommandUser should have it's default documented Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component:

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

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

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

https://bugzilla.mindrot.org/show_bug.cgi?id=2354 Bug ID: 2354 Summary: please document that PermitRootLogin really checks for uid=0 Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Documentation

https://bugzilla.mindrot.org/show_bug.cgi?id=2310 Bug ID: 2310 Summary: functionality to start process before ssh and/or to "wrap" such command around ssh Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5