similar to: Write.table eol argument

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

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

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

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

How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that can't do PAM, perhaps NIS is the way to go (assuming, of course, you're behind a firewall). You can store login information in LDAP like you want, then use a home-grown script to extract the information to a NIS map. Or, if you have a Solaris 8 machine lying around, you can cut out the middle step and use

Hi all, I have problems reading Unicode (UTF-16) coded tables in R 2.8.1 under Windows Vista. Imagine the following table: a b c d X 1,2 1,3 1,4 Y 2,2 2,3 2,4 Z 3,2 3,3 3,4 Usually I would use the following code to read the table: t = read.table("test.txt", header=T, sep="\t",dec=",") This works well if I create the table

> Just in case it's not clear, the svn for that page is part of the > llvmCore project. Specifically, > > https://llvm.org/svn/llvm-project/llvm/trunk/docs/GettingStarted.html > > Thanks for offering to help with the documentation. Making things > clearer for new users is always a good thing. > > Regards, > Jim If I do a sparse checkout like >svn co

I am trying to write a "thumbnailer" for the thunar file manager that can process .ogg files containing a video stream and produce a thumbnail of a particular frame. The only trouble is telling which files have a video stream in an efficient method. The best I've come up with is running ogginfo on every file with the mimetype application/ogg. Is there a better method? I know

I have everything installed via Darwin ports. When I try to do a "script/plugin install engines" in a freshly created rails app I get the following: Macintosh:~/My Web Sites/nckapool bill$ script/plugin install engines svn: PROPFIND request failed on ''/rails/plugins'' svn: PROPFIND of ''/rails/plugins'': 403 Forbidden (http:// svn.protocool.com)

Hola a todos: Tengo un problemita y no se como solucionarlo, uso macosx 10.5, de apple el leopard que es Unix, leo una base de datos mysql desde R, luego escribo un archivo de la siguiente forma: write.table(paraBlup, file="paraBlup", sep="\t", eol="\r\n") Este archivo lo abro desde una aplicación escrita en fortran, que compile con gfortran para mac. Al

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

Please, we do need complete reproduction instructions (and not speculation) as the FAQ asks. 1) How exactly did you read the file in? 2) 'longer' than what? 3) What line ending is this? I've just tried loading a 1000-line 50kb file using the 'Open Script' menu item, and it worked with CRLF, LF or CR line endings. Some guesses are that there are control characters in the

I have a text file that is UTF-16LE encoded with CRLF line endings and '@' as field separators that I want to read in R on a Linux system. Which would be fine as read.table("foo.txt", file.encoding = "UTF-16LE", sep = "@", ...) *except* that the data may contain the LF character which R treats as end-of-line and then barfs that there are too few elements

Colleagues, I am using R 2.7.2 on all three platforms (OS X; Windows; Linux) and I have encountered the following problem: I use R to issue a system call the execute a command in the OS. For example: system("DOSOMETHING TOSOMEFILE") In most situations, this task completes successfully and control returns to R. However, in rare situations, the target file (TOSOMEFILE) is

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

Since December 2014, clients using the Python poplib library (getmail in my case) started to limit the line length of RETR and other command responses sent from the server to 2048 bytes: See https://bugs.python.org/issue16041 (Included at least in Python-2.7.9) Dovecot doesn't have line split in the POP3 module, so Python fails to retrieve messages with long lines. RFC 1939 says: "

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

Hello everyone, I'm using the very good imaptest [0] tool to test my little imap server implementation. I've tried to use the dovecot-crlf [1] file, but it looks like there are some major issues : $ grep -n "In-Reply-To.*;" tests/data/dovecot-crlf 479:In-Reply-To: <20020806175441.GA7148 at linux.taugt.net>; from rueckert at informatik.uni-rostock.de on Tue, Aug 06, 2002

Hi, we are migrating from Cyrus 2.3.7 to Dovecot 2.2.13. We have ~7000 maildirs with ~500GB. Our goal is to do the migration without users have notice and with the shortest service downtime. The users use IMAP (with shared folders and ACL), POP3 and sieve filters. As a first choice, we tried the Dovecot's dsync tool. First tests were great, but we are not able to change the Cyrus auth

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