similar to: CRLF/LF Conversion

Displaying 20 results from an estimated 900 matches similar to: "CRLF/LF Conversion"

2005 Apr 27
0
RE: CRLF << -- >> LF
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.
2020 Jul 25
0
Guidelines when to use LF vs CRLF ("\n" vs. "\r\n") on Windows for new lines (line endings)?
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
2003 Oct 30
0
[PATCH] contrib/cygwin/ssh-host-config: Fix a CRLF/LF issue
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.
2013 May 21
3
should dovecot store maildir files with CRLF or LF?
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
2020 Jul 25
2
Guidelines when to use LF vs CRLF ("\n" vs. "\r\n") on Windows for new lines (line endings)?
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
1998 Jul 08
0
fixcrlf doesn't seem to fix crlf
I installed Fixcrlf.exe from the Samba site. I tried it out on my NT 4.0 station, but it doesn't seem to accomplish anything. Specifically: - I bring up a file in Notepad - the text is one long line with black squares at the end of records, indicating that there are LF's but not CRLF's. - I drag the file icon from Explorer on to the FixCRLF icon and am rewarded with an
2006 Aug 01
1
Inconsistent handling of CRLF in APPEND
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
2019 Apr 15
1
No CRLF in Pigeonhole's header?
Hello, I have been told on Freenode's #dovecot to ask here. I have Exim 4.92 complaining about "Non-CRLF-terminated header, under CHUNKING: message abandoned" with redirects made by Pigeonhole 0.5.5 (with Dovecot 2.3.5.1). Please find relevant part of the traffic below, and help me determine whether Exim is correct on this. ? 0x0000:? 4500 0954 0000 4000 8006 0000 7f00 0001? E..T..
2012 Jun 26
1
Wrong headers in dovecot-crlf
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
2004 May 05
0
Why are error messages CRLF terminated?
Hi, why uses openssh for printing error messages CRLF termination? Petr
2008 Jun 13
0
1.1rc10: istream-crlf.c: assertion failed: (size != 0)
Hi, I am migrating from 0.99.14 to 1.1.rc10 and from mbox to maildir. During the conversion, via convert plugin, I get this assertion failure: 2008-06-13 14:12:51 Error: IMAP(username): Next message unexpectedly lost from 4700 2008-06-13 14:12:51 Error: IMAP(username): Next message unexpectedly lost from 4700 2008-06-13 14:12:51 Panic: IMAP(username): file istream-crlf.c: line 49
2000 Mar 08
1
Stripping/Prevent CRLF
I thought I had read somewhere that you can prevent the adding of the ^M's when copying a file to a samba share. (Such as doing an ascii ftp) Now I cannot find where I read this. I have a constant need to transfer excel files containing data to be uploaded and want to use samba to get these to the server. Can this be configured into Samba. I am using 2.0.6 on Solaris 2.6. When using
2020 Jan 16
0
[PATCH 1/2] Win::Hivex::Regedit: Accept CRLF line endings
--- perl/lib/Win/Hivex/Regedit.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/perl/lib/Win/Hivex/Regedit.pm b/perl/lib/Win/Hivex/Regedit.pm index 34426f1..2b17036 100644 --- a/perl/lib/Win/Hivex/Regedit.pm +++ b/perl/lib/Win/Hivex/Regedit.pm @@ -144,6 +144,7 @@ sub reg_import # this is fairly common in pasted regedit files. $lineno++; chomp; + s/\r$//;
2018 Oct 30
0
Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)
Op 28-10-2018 om 23:28 schreef Peter Nabbefeld: > Hello, > > cannot fetch mails from an IMAP folder because of the error in the > subject - fetching always stops with SIGABRT. > > Could anybody help me, please? We need more information than that: - Your configuration and version, which is privided by the output from `dovecot -n` - Steps to reproduce, e.g the email message and
2018 Oct 30
1
Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)
Am 30.10.18 um 13:37 schrieb Stephan Bosch: > > > Op 28-10-2018 om 23:28 schreef Peter Nabbefeld: >> Hello, >> >> cannot fetch mails from an IMAP folder because of the error in the >> subject - fetching always stops with SIGABRT. >> >> Could anybody help me, please? > > We need more information than that: > > - Your configuration and
2018 Oct 28
2
Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)
Hello, cannot fetch mails from an IMAP folder because of the error in the subject - fetching always stops with SIGABRT. Could anybody help me, please? Kind regards Peter
2010 Sep 13
4
Problem with WARNING...headers with CRLF line endings
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
2002 Feb 19
4
CR instead of CR/LF
New to Samba, so excuse me if this is a stupid question, but I've searched the different on line resources and can't find an answer. When I copy Perl scripts from my Windows 2000 machine to the UNIX Samba share on that same machine, a CR/LF appears at the end of each line instead of just the CR, making UNIX unhappy when I go to run those scripts. Any way to have Samba strip the LF
2000 Jan 28
2
CR/LF proposal
Hi, I'm new on this list, and just skimmed through the archives, so I appologize if this has been requested before. I read in the FAQ that you do not convert. LF to CR/LF because there is no sure way of knowing what type of file something is. I could see that this would cause problems if you converted a binary file or some other data file. But what if you assign a directory that would always
2005 Jul 10
0
package loading smooth.lf (LOCFIT), couldn't find functio n "smooth.lf"
The version of locfit on the web site mentioned apparently has been revised by Prof. Loader, and is newer than the CRAN version that I have been maintaining. If Prof. Loader is OK with it, I will take a look and see if I can get the new version into CRAN-conforming form and upload to CRAN. Meanwhile, make sure you're using the package from Prof. Loader's web page, instead of the one on