3348
Comment: add the perl command for deleting lines, and link to UsingFind
|
4397
All the ed commands were broken.
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
[[Anchor(faq21)]] | <<Anchor(faq21)>> |
Line 3: | Line 3: |
{{{sed}}} is a good command to replace strings, e.g. | {{{ed}}} is the standard UNIX command-based editor. Here's three commonly-used syntaxes for replacing the string `olddomain.com` by the string `newdomain.com` in a file named `file`. All three commands do the same although the last two incur the minor additional overhead of a subshell. |
Line 6: | Line 6: |
sed 's/olddomain\.com/newdomain.com/g' input > output | # ed -s file <<< $'g/olddomain\.com/s//newdomain.com/g\nw' # printf '%s\n' 'g/olddomain\.com/s//newdomain.com/g' w | ed -s file # printf 'g/olddomain\.com/s//newdomain.com/g\nw' | ed -s file |
Line 12: | Line 14: |
for i in *; do sed 's/old/new/g' "$i" > atempfile && mv atempfile "$i" |
for file in ./*; do ed -s "$file" <<< $'g/old/s//new/g\nw' |
Line 17: | Line 19: |
GNU sed 4.x has a special {{{-i}}} flag which makes the loop and temp file unnecessary: | To do this recursively, the best way would be to enable globstar in bash 4 (`shopt -s globstar`, a good idea to put this in your `~/.bashrc`) and use: {{{ for file in ./**/*; do ed -s "$file" <<< $'g/old/s//new/g\nw' done }}} If you don't have bash 4, you can use find. Unfortunately, it's a bit tedious to feed ed stdin for each file hit: |
Line 20: | Line 29: |
sed -i 's/old/new/g' * | find . -type f -exec bash -c 'printf "%s\n" "g/old/s//new/g" w | ed -s "$1"' -- {} \; |
Line 23: | Line 32: |
On some (but not all) BSD systems, sed has a {{{-i}}} flag as well, but it takes a mandatory argument. The above example then becomes | {{{sed}}} is a '''Stream EDitor''', not a '''file''' editor. Nevertheless, people everywhere tend to abuse it for trying to edit files. It doesn't edit files. GNU's `sed` (and some BSD `sed`'s) have a `-i` option that makes a copy and replaces the original file with the copy. An expensive operation, but if you enjoy unportable code, I/O overhead and bad side effects (such as destroying symlinks), this would be an option: |
Line 26: | Line 35: |
sed -i '' 's/old/new/g' * | # sed -i 's/old/new/g' ./* # GNU # sed -i '' 's/old/new/g' ./* # BSD # for file in ./*; do sed 's/old/new/g' "$file" > "$file~"; mv "$file~" "$file"; done # Others |
Line 28: | Line 39: |
which in turn does not work with GNU sed. Effectively, whenever portability matters, {{{sed -i}}} should be avoided. |
|
Line 34: | Line 43: |
perl -pi -e 's/old/new/g' * | perl -pi -e 's/old/new/g' ./* |
Line 37: | Line 46: |
Recursively (requires GNU or BSD {{{find}}}): | Recursively using find: |
Line 40: | Line 49: |
find . -type f -print0 | xargs -0 perl -pi -e 's/old/new/g' | find . -type f -exec perl -pi -e 's/old/new/g' {} + |
Line 46: | Line 55: |
perl -ni -e 'print unless /foo/' * | perl -ni -e 'print unless /foo/' ./* |
Line 53: | Line 62: |
find . -type f -print0 | xargs -0 perl -i.bak -pne \ 's/\bunsigned\b(?!\s+(int|short|long|char))/unsigned long/g' |
find . -type f -exec perl -i.bak -pne \ 's/\bunsigned\b(?!\s+(int|short|long|char))/unsigned long/g' {} + |
Line 68: | Line 77: |
[ $# -lt 1 ] && set -- * | [ $# -lt 1 ] && set -- ./* |
Line 75: | Line 84: |
sed "s|$old|$new|g" "$file" > "$file"-new || exit | sed "s|$old|$new|g" -- "$file" > "$file"-new || exit |
Line 77: | Line 86: |
if cmp "$file" "$file"-new >/dev/null 2>&1 then rm "$file"-new # file has not changed else mv "$file"-new "$file" # file has changed: overwrite original file |
if cmp -- "$file" "$file"-new >/dev/null 2>&1 then rm -- "$file"-new # file has not changed else mv -- "$file"-new "$file" # file has changed: overwrite original file |
Line 91: | Line 100: |
* use another {{{sed}}} separator character than '|', e.g. ^A (ASCII 1) * the [:UsingFind:find] command above could use either {{{xargs}}} or the built-in {{{xargs}}} of POSIX find |
* use another {{{sed}}} separator character than '|', e.g. ^A (ASCII 0x01) * the [[UsingFind|find]] command above could use either {{{xargs}}} or the built-in {{{xargs}}} of POSIX find |
Line 94: | Line 103: |
Note: {{{set -- *}}} in the code above is safe with respect to files whose names contain spaces. The expansion of * by {{{set}}} is the same as the expansion done by {{{for}}}, and filenames will be preserved properly as individual parameters, and not broken into words on whitespace. | Note: {{{set -- ./*}}} in the code above is safe with respect to files whose names contain spaces. The expansion of `./*` by {{{set}}} is the same as the expansion done by {{{for}}}, and filenames will be preserved properly as individual parameters, and not broken into words on whitespace. |
Line 97: | Line 106: |
---- CategoryShell |
How can I replace a string with another string in all files?
ed is the standard UNIX command-based editor. Here's three commonly-used syntaxes for replacing the string olddomain.com by the string newdomain.com in a file named file. All three commands do the same although the last two incur the minor additional overhead of a subshell.
# ed -s file <<< $'g/olddomain\.com/s//newdomain.com/g\nw' # printf '%s\n' 'g/olddomain\.com/s//newdomain.com/g' w | ed -s file # printf 'g/olddomain\.com/s//newdomain.com/g\nw' | ed -s file
To replace a string in all files of the current directory:
for file in ./*; do ed -s "$file" <<< $'g/old/s//new/g\nw' done
To do this recursively, the best way would be to enable globstar in bash 4 (shopt -s globstar, a good idea to put this in your ~/.bashrc) and use:
for file in ./**/*; do ed -s "$file" <<< $'g/old/s//new/g\nw' done
If you don't have bash 4, you can use find. Unfortunately, it's a bit tedious to feed ed stdin for each file hit:
find . -type f -exec bash -c 'printf "%s\n" "g/old/s//new/g" w | ed -s "$1"' -- {} \;
sed is a Stream EDitor, not a file editor. Nevertheless, people everywhere tend to abuse it for trying to edit files. It doesn't edit files. GNU's sed (and some BSD sed's) have a -i option that makes a copy and replaces the original file with the copy. An expensive operation, but if you enjoy unportable code, I/O overhead and bad side effects (such as destroying symlinks), this would be an option:
# sed -i 's/old/new/g' ./* # GNU # sed -i '' 's/old/new/g' ./* # BSD # for file in ./*; do sed 's/old/new/g' "$file" > "$file~"; mv "$file~" "$file"; done # Others
Those of you who have perl 5 can accomplish the same thing using this code:
perl -pi -e 's/old/new/g' ./*
Recursively using find:
find . -type f -exec perl -pi -e 's/old/new/g' {} +
If you want to delete lines instead of making substitutions:
perl -ni -e 'print unless /foo/' ./* # Deletes any line containing the perl regex foo
To replace for example all "unsigned" with "unsigned long", if it is not "unsigned int" or "unsigned long" ...:
find . -type f -exec perl -i.bak -pne \ 's/\bunsigned\b(?!\s+(int|short|long|char))/unsigned long/g' {} +
Finally, for those of you with none of the useful things above, here's a script that may be useful:
#!/bin/sh # chtext - change text in several files # neither string may contain '|' unquoted old='olddomain\.com' new='newdomain\.com' # if no files were specified on the command line, use all files: [ $# -lt 1 ] && set -- ./* for file do [ -f "$file" ] || continue # do not process e.g. directories [ -r "$file" ] || continue # cannot read file - ignore it # Replace string, write output to temporary file. Terminate script in case of errors sed "s|$old|$new|g" -- "$file" > "$file"-new || exit # If the file has changed, overwrite original file. Otherwise remove copy if cmp -- "$file" "$file"-new >/dev/null 2>&1 then rm -- "$file"-new # file has not changed else mv -- "$file"-new "$file" # file has changed: overwrite original file fi done
If the code above is put into a script file (e.g. chtext), the resulting script can be used to change a text e.g. in all HTML files of the current and all subdirectories:
find . -type f -name '*.html' -exec chtext {} \;
Many optimizations are possible:
use another sed separator character than '|', e.g. ^A (ASCII 0x01)
the find command above could use either xargs or the built-in xargs of POSIX find
Note: set -- ./* in the code above is safe with respect to files whose names contain spaces. The expansion of ./* by set is the same as the expansion done by for, and filenames will be preserved properly as individual parameters, and not broken into words on whitespace.
A more sophisticated example of chtext is here: http://www.shelldorado.com/scripts/cmds/chtext