line-endings

On Windows this #include <stdio.h> int main() { putc('A',stdout); putc('\r',stdout); putc('\n',stdout); } outputs A<CR><CR><LF> How to write just LF char to stdout without automatic conversion to CR LF? I need it to make simple socket stream reader to stdout. I've tried bcc32 from CodeGear, mingw, tinycc all yield same result, changing putc to putchar, fputc, fwrite doesn't help either. The MSVC solution is: #include <io.h> #include <fcntl.h> ... _setmode(1,_O_BINARY) Other runtimes may provide the C99 solution or an alternate way. EDIT: I believe setmode([file number],O_BINARY) originated on

I'm using C# and am trying to output a few lines to an ASCII file. The issue I'm having is that my Linux host is seeing these files as: ASCII text, with CRLF line terminators I need this file to be just: ASCII text The CRLF is causing some issues and I was hoping there was a way in C# to just create the file formatted in the way I want. I'm basically using this code: string[] lines = { "Line1", "Line2" }; File.WriteAllLines(myOutputFile, lines, System.Text.Encoding.UTF8); Is there an easy way to create the file without the CRLF line terminators? I can probably take care of it on the Linux side

Environment: Windows + PhpStorm Issue : PhpStorm saves file with Windows line endings - and for shell script it's issue so there is need to always convert after copying to server. Question : Is possible to configure PhpStorm to save file with Linux line endings - \n and not \n\r (new line + carriage return)? You can safely use \n line ending for .php and most of other files as well -- PHP on Windows will read such files just fine. To set default line ending for all new files: go to Settings/Preferences | Editor | Code Style and change Line separator (for new files) option to the desired style

I understand the difference between the two so there's no need to go into that, but I'm just wondering what the reasoning is behind why Windows uses both CR and LF to indicate a line break. It seems like the Linux method (just using LF) makes a lot more sense, saves space, and is easier to parse. Historically when using dot-matrix printers teletypes CR would return the carriage to the first position of the line while LF would feed to the next line. Using CR+LF in the file themselves made it possible to send a file directly to the printer, without any kind of printer driver. Thanks @zaph

Is there an easy way to get the type of line ending that the current operating system uses? If you are operating on a file that you opened in text mode, then you are correct that line breaks all show up as ' \n '. Otherwise, you are looking for os.linesep . From http://docs.python.org/library/os.html : os. linesep The string used to separate (or, rather, terminate) lines on the current platform. This may be a single character, such as '\n' for POSIX, or multiple characters, for example, '\r\n' for Windows. Do not use os.linesep as a line terminator when writing files opened in text mode (the

How do I make git status ignore line ending differences? Background info: I use randomly Windows and Linux to work on the project. The project is in Dropbox. I found a lot about how do make git diff ignore line endings. Since i use meld git diff opens meld for each file. And meld says "identical file". So how do I avoid this. Git should only open meld for changed files. And git status should not report files as changed if only the file ending is different. EDIT: Cause: This happened because of this setting on Windows core.autocrlf true So I checked out the working copy on Linux and set core