18

I exported results in a text file from a program running on Windows 7, and copied the file on Xubuntu 14.04. In a terminal, I ran dos2unix file.txt, which tells me converting file out_mapqtl.txt to Unix format. However, when I look at the file with less, I still see the Windows end-of-line as ^M, and wc -l returns me "0".

I tried several things described here, but none works. I then opened the file in Vim and did :%s/\r/\r/g as explained there, which worked fine. So any idea why dos2unix didn't work? Would there be a way to avoid opening Vim every time?

Community
  • 1
  • 1
tflutre
  • 3,354
  • 9
  • 39
  • 53
  • 1
    A bit late here... But I wrote a small program that makes life easier than dos2unix when you're not sure about the input format, or when input formats are intermingled : https://github.com/mdolidon/endlines – Mathias Dolidon Jul 12 '15 at 09:45
  • @MathiasDolidon Thank you, Mathias! – isomorphismes May 12 '18 at 01:57
  • Your question can be rephrased as: Why _doesn't_ dos2unix modify a _text_ file? ~ * ~ Here is a question asking the opposite: [Why _does_ dos2unix modify a _binary_ file?](https://stackoverflow.com/q/34257924) ~ * ~ A simple answer to both questions is: **because dos2unix isn't foolproof**. – Henke Oct 22 '22 at 16:31

4 Answers4

20

I know you have gotten this resolved, but I wanted to add a note for reference, based on some testing I've done.

If less is showing ^M, then like Sybren I suspect it is a MAC style ending (\r), not DOS (\r\n). You can determine that easily using cat:

$ cat -e filename

  • Unix endings (\n) show as $
  • MAC endings (\r) show as ^M (less shows these)
  • DOS\Windows endings (\r\n) show as ^M$ (less does not appear to show these)

Use dos2unix to get rid of the DOS (^M$) endings

Use mac2unix to get rid of the MAC (^M) endings - dos2unix won't get rid of these.

I had a file where I had to use dos2unix and mac2unix to get rid of all the non-Unix endings.

em_bo
  • 624
  • 7
  • 13
  • thanks for this answer, I was stumped running dos2unix, didn't realise the file was using the old mac line endings somehow. – Pellet May 24 '17 at 00:08
14

\r denotes a carriage return, and on MAC it is used without \n to denote a line break. Are you sure the file is in DOS (\r\n) format and not MAC (\r)?

If VIM really turns out to be the only thing that'll repair your files, you can also invoke it as:

vim somefile.txt +"%s/\r/\r/g" +wq

This will open the file, perform the operation, save it, then quit.

Can you give us an example of the file, so that we can investigate further?

dr. Sybren
  • 829
  • 5
  • 18
  • sorry for the delay of my answer. The file was produced on Windows 7, thus I assume it is in the DOS format. I'm not even sure the program runs on Mac. By the way, the program is called [MapQTL](http://www.kyazma.nl/index.php/mc.MapQTL/). Anyway, my problem is now solved, thanks. – tflutre May 27 '14 at 09:36
  • Thanks for letting us know your problem has been solved, and accepting my solution as the answer. – dr. Sybren Jun 02 '14 at 12:43
  • hi, what does " %s/\r/\r/g" do ? it looks like sed expression . replace '\r' with "\r"? – nathan Dec 08 '16 at 00:26
  • 1
    yup, that's what it does. The `%` in front applies the expression to all lines in the file. Due to the line-ending-handling magic of VIM, this seemingly useless expression apprarently does something. – dr. Sybren Dec 11 '16 at 04:05
1

Try this:

tr -d '\r' < file
Mark Setchell
  • 191,897
  • 31
  • 273
  • 432
0

I have used Notepad++ feature: Edit>EOL Conversions>Unix(LF).

Now export this file to the Unix machine using pscp.exe.

Let me know if that worked for you.

Yogi
  • 609
  • 1
  • 8
  • 21
Shadow79art
  • 1
  • 1