I run sed to do some substitution on windows and I noticed that it automatically converts line endings to Unix (\n). Is there an option to tell sed to use Windows line endings (\r\n) or even better to preserve the line endings from the file?
Note: I use sed from unxutils: http://unxutils.sourceforge.net/
LC_ALL=C perl -i -e 'binmode $STDIN;undef $/;$_=<>;s|http://911coned.com|https://911coned.com|gm;print' education.html
git diff
program.
You can use the -b
option for sed to have it treat the file as binary. This will fix the problem with cygwin's sed on Windows.
Example: sed -b 's/foo/bar/'
If you wish to match the end of the line, remember to match, capture and copy the optional carriage return.
Example: sed -b 's/foo\(\r\?\)$/bar\1/'
From the sed man page:
-b --binary This option is available on every platform, but is only effective where the operating system makes a distinction between text files and binary files. When such a distinction is made—as is the case for MS-DOS, Windows, Cygwin—text files are composed of lines separated by a carriage return and a line feed character, and sed does not see the ending CR. When this option is specified, sed will open input files in binary mode, thus not requesting this special processing and considering lines to end at a line feed.`
You could try to sub the \n
for \r\n
at the end of your existing script like so:
sed 's/foo/bar/;s/$/\r/'
or perhaps
sed -e 's/foo/bar/' -e 's/$/\r/'
If neither of the above two work, you'll have to consult the specific man page for your version of sed
to see if such an option exists. Note that the *nix versions of sed
do not alter the line terminators without being told to do so.
Another alternative is to use the cygwin
version of sed
which shouldn't have this undesirable behavior.
0x0A
) and \r\n (0x0D 0x0A
) - this proposed solution (of always re-injecting the \r) breaks it.
Alternatively, (the cygwin version of) perl -pe
doesn't seem to have this problem.
sed -i -e 's/<img[^>]*\/>//g' *.xml
replaces line endings by '\n' perl -i -p -e 's/<img[^>]*\/>//g' *.xml
preserves the original line endings
Gnuwin can be suppressed to mess up the newlines (win->unix) if you only specify the -b switch and redirect. Using the -i (inline) switch will mess it up.
E.g. sed.exe -b "s/\xFF\xFE//" c:\temp\in.csv > c:\temp\out.csv
-i
mode in my answer.
I've found that sed-4.4.exe
from https://github.com/mbuilov/sed-windows is pure win as it
uses windows CRLF line endings in default mode
preserves original line endings in -b mode
works correctly with in-place -i mode
also offers -z mode with \0 delimeters instead of \n which may be handy sometimes too
See also list of sed options and list of all windows sed ports.
Note that gnuwin32 sed 4.2.1 does corrupt line endings in -bi
mode and doesn't have -z
mode at all.
Success story sharing
sed -i
on cygwin (for me), but you can work around that. Thanks for the update -- the other answers were the last word on this subject for a while.sed -i
: it is just important how to type it. Whilesed -bi
andsed -i -b
work,sed -ib
does not work: see the man page for why (uses theb
as the suffix for the backup copy).sed -bi 's/foo/bar/'