有趣的是，在Windows上的Git Bash中，sed ""已经做到了:

$ echo -e "abc\r" >tst.txt
$ file tst.txt
tst.txt: ASCII text, with CRLF line terminators
$ sed -i "" tst.txt
$ file tst.txt
tst.txt: ASCII text

我的猜测是，sed在从输入读取行时忽略它们，并且总是将Unix行结束符写入输出。

如果您没有访问dos2unix的权限，但是可以阅读这个页面，那么您可以从这里复制/粘贴dos2unix.py。

#!/usr/bin/env python
"""\
convert dos linefeeds (crlf) to unix (lf)
usage: dos2unix.py <input> <output>
"""
import sys

if len(sys.argv[1:]) != 2:
  sys.exit(__doc__)

content = ''
outsize = 0
with open(sys.argv[1], 'rb') as infile:
  content = infile.read()
with open(sys.argv[2], 'wb') as output:
  for line in content.splitlines():
    outsize += len(line) + 1
    output.write(line + '\n')

print("Done. Saved %s bytes." % (len(content)-outsize))

(超级用户交叉发布。)

The solutions posted so far only deal with part of the problem, converting DOS/Windows' CRLF into Unix's LF; the part they're missing is that DOS use CRLF as a line separator, while Unix uses LF as a line terminator. The difference is that a DOS file (usually) won't have anything after the last line in the file, while Unix will. To do the conversion properly, you need to add that final LF (unless the file is zero-length, i.e. has no lines in it at all). My favorite incantation for this (with a little added logic to handle Mac-style CR-separated files, and not molest files that're already in unix format) is a bit of perl:

perl -pe 'if ( s/\r\n?/\n/g ) { $f=1 }; if ( $f || ! $m ) { s/([^\n])\z/$1\n/ }; $m=1' PCfile.txt

注意，这将把文件的统一版本发送到标准输出。如果你想用一个统一的版本替换这个文件，添加perl的-i标志。

这对我很有效

tr "\r" "\n" < sampledata.csv > sampledata2.csv 

在Linux上，使用sed很容易将^M (Ctrl + M)转换为*nix换行符(^J)。

在CLI中就像这样，文本中会有一个换行符。然而，\将^J传递给sed:

sed 's/^M/\
/g' < ffmpeg.log > new.log

你可以使用^V (Ctrl + V)， ^M (Ctrl + M)和\(反斜杠)当你输入:

sed 's/^V^M/\^V^J/g' < ffmpeg.log > new.log

安装dos2unix，然后就地转换文件

dos2unix <filename>

将转换后的文本输出到不同的文件使用

dos2unix -n <input-file> <output-file>

你可以在Ubuntu或Debian上安装它

sudo apt install dos2unix

或者在macOS上使用Homebrew

brew install dos2unix