mjhjmtu

Most UNIX operating systems have a utility called dos2unix that will convert the CRLF to LF. The other answers cover the "what are they" question.

A simpler way to do this is to use the following command:

dos2unix filename

This command works with path patterns as well, Eg

dos2unix path/name*

If it doesn't work, try using different mode:

dos2unix -c mac filename

• 
  -c Set conversion mode. Where CONVMODE is one of: ascii, 7bit, iso, mac with ascii being the default.

This worked for me

:e ++ff=dos 

then

:set ff=unix 

and finally

:wq 

Another way to get rid of carriage returns is with the tr command.

I have a small script that look like this

#!/bin/sh
tmpfile=$(mktemp)
tr -d 'r' <"$1" >"$tmpfile"
mv "$tmpfile" "$1"

You can clean this up with sed:

sed -e 's/^M$//' < infile > outfile

The trick is how to enter the carriage-return properly. Generally, you need to type C-v C-m to enter a literal carriage return. You can also have sed work in place with

sed -i.bak -e 's/^M$//' infile

In my case,

Nothing above worked, I had a CSV file copied to Linux machine from my mac and I used all the above commands but nothing helped but the below one

tr "15" "n" < inputfile > outputfile

I had a file in which ^M characters were sandwitched between lines something like below

Audi,A4,35 TFSi Premium,,CAAUA4TP^MB01BNKT6TG,TRO_WBFB_500,Trico,CARS,Audi,A4,35 TFSi Premium,,CAAUA4TP^MB01BNKTG0A,TRO_WB_T500,Trico,

What is this ^M?

The ^M is a carriage-return character. If you see this, you're probably looking at a file that originated in the DOS/Windows world, where an end-of-line is marked by a carriage return/newline pair, whereas in the Unix world, end-of-line is marked by a single newline.

How could it have got there?

When there is change in file format.

How do I get rid of it?

open your file with

vim -b FILE_PATH

save it with following command

:%s/^M//g

You can use Vim in Ex mode:

ex -bsc '%s/r//|x' file

1. -b binary mode




2. % select all lines




3. s substitute




4. r carriage return




5. x save and close

In the past, I have seen even configuration files are not parsed properly and complain about whitespace, but if you vi and do a set list it won't show the whitespace, grep filename [[space]] will show you ^M

that's when dos2unix file helps

None of the options here worked for me.

Finally opened the file in MS Word, and voila the ^M disappeared. Cut and paste to any other editor of your choice.