line-endings

Following situation: I'm working on a Mac running OS X and recently joined a project whose members so far all use Windows. One of my first tasks was to set up the codebase in a Git repository, so I pulled the directory tree from FTP and tried to check it into the Git repo I had prepared locally. When trying to do this, all I got was this fatal: CRLF would be replaced by LF in blog/license.txt. Since this affects all files below the "blog" folder, I'm looking for a way to conveniently convert ALL files in the tree to Unix line-endings. Is there a tool that does that out of the box or do I get

Visual Studio occasionally tells me: The line endings in the following files are not consistent. Do you want to normalize the line endings? It then gives me a drop down with different standards or something, such as Windows, Mac, Unix, and a couple of Unicode ones. What does this mean and what is going to happen if I click Yes ? What that usually means is that you have lines ending with something other than a carriage return/line feed pair. It often happens when you copy and paste from a web page into the code editor. Normalizing the line endings is just making sure that all of the line ending

I was trying to use the following code to read lines from a file. But when reading a file , the contents are all in one line: line_num=0 File.open('xxx.txt').each do |line| print "#{line_num += 1} #{line}" end But this file prints each line separately. I have to use stdin, like ruby my_prog.rb < file.txt , where I can't assume what the line-ending character is that the file uses. How can I handle it? Olivier L. I believe my answer covers your new concerns about handling any type of line endings since both "\r\n" and "\r" are converted to Linux standard "\n" before parsing the lines. To support

I'm trying to install YouCompleteMe from here . When I execute: ./install.sh --clang-completer I get this error: env: bash\r: No such file or directory I don't know whats wrong with environment variables. Here's my bash path: which bash /bin/bash Do I need to change it to /usr/bash? If yes, then how should I do that? I tried changing ~/.bashrc file, but it didn't work. The error message suggests that the script you're invoking has embedded \r characters , which in turn suggests that it has Windows-style \r\n line endings instead of the \n -only line endings bash expects. As a quick fix , you

I have cloned a repository that had inconsistend line endings. I have added a .gitattributes that sets the text attribute for the files I want to normalize. Now when I commit changes I get the message: warning: CRLF will be replaced by LF in FILE. The file will have its original line endings in your working directory. How can I make git normalize my working copy of the file for me? Preferably I would like git to normalize the entire working tree. With Git client 2.16 and higher there is now a much simpler way to do this. Just use git add --renormalize . For those using v2.16 or better, you can

Why did DOS/Windows and Mac decide to use \r\n and \r for line ending instead of \n? Was it just a result of trying to be "different" from Unix? And now that Mac OS X is Unix (-like), did Apple switch to \n from \r? 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 move to the next line (LF = line feed). The