\n is converted to os.linesep for files opened in text-mode. So when you write os.linesep to a text-mode file on Windows, you write \r\n, and the \n gets converted resulting in \r\r\n. See also the docs: Do not use os.linesep as a line terminator when writing files opened in text mode (the default); use a … Read more
That functionality is already built into Notepad++. From the “Edit” menu, select “EOL Conversion” -> “UNIX/OSX Format”. screenshot of the option for even quicker finding (or different language versions) You can also set the default EOL in notepad++ via “Settings” -> “Preferences” -> “New Document/Default Directory” then select “Unix/OSX” under the Format box.
The Replace dialog can handle extended characters like EOL. Just change “Search Mode” to “Extended”, and you can work with EOL (\r\n in Windows or \n in Unix), tabs (\t), etc. You can also use the Find in Files tab of the dialog to do the replace across multiple files.
Command :%s/<Ctrl-V><Ctrl-M>/\r/g Where <Ctrl-V><Ctrl-M> means type Ctrl+V then Ctrl+M. Explanation :%s substitute, % = all lines <Ctrl-V><Ctrl-M> ^M characters (the Ctrl-V is a Vim way of writing the Ctrl ^ character and Ctrl-M writes the M after the regular expression, resulting to ^M special character) /\r/ with new line (\r) g And do it globally … Read more
DOS inherited CR-LF line endings (what you’re calling \r\n, just making the ascii characters explicit) from CP/M. CP/M inherited it from the various DEC operating systems which influenced CP/M designer Gary Kildall. CR-LF was used so that the teletype machines would return the print head to the left margin (CR = carriage return), and then … Read more
The differences between binary and text modes are implementation defined, but only concern the lowest level: they do not change the meaning of things like << and >> (which insert and extract textual data). Also, formally, outputting all but a few non-printable characters (like ‘\n’) is undefined behavior if the file is in text mode. … Read more
The regex I use when I want to be precise is “\r\n?|\n”. When I’m not concerned about consistency or empty lines, I use “[\r\n]+”, I imagine it makes my programs somewhere in the order of 0.2% faster.
For any new document: Settings -> Preferences -> New Document (left pane) -> New Document (right pane) -> Format (Line ending) -> Windows (CR LF) / Unix (LF) / Macintosh (CR) And for an already-open document: Edit -> EOL Conversion
This is a classic issue: (picture from Luis Tubes‘s blog post) The usual fix is to convert those files yourself, with dos2unix or Swiss File Knife. I have always preferred to keep core.autocrlf to false, which means: git config –global core.autocrlf false
Use the PHP_EOL constant, which is automatically set to the correct line break for the operating system that the PHP script is running on. Note that this constant is declared since PHP 5.0.2. <?php echo “Line 1” . PHP_EOL . “Line 2”; ?> For backwards compatibility: if (!defined(‘PHP_EOL’)) { switch (strtoupper(substr(PHP_OS, 0, 3))) { // … Read more