When piping output of find to xargs, always use -print0 option of find and -0 option of xargs. This allows processing files with any allowed characters in names (spaces, new lines etc.). (However I prefer -exec.)
There’s an i command to insert a line in sed, it is better to use it instead of s/^/...\n/. It makes code more readable (if we can talk about readability of sed code, huh).
If you want to split a delimiter separated line and print some field, you need cut. Keep awk for more complicated tasks.
If you want to split a delimiter separated line and print some field, you need cut. Keep awk for more complicated tasks.
Depends on the delimiter too! For anyone else reading this, sed accepts many kinds of delimiters. sed "s@thing@thing2@g" file.txt is valid. I use this sometimes when parsing/replacing text with lots of slashes (like directory lists) so I can avoid escaping a ton of stuff.
My 5 cents:
When piping output of
findtoxargs, always use-print0option offindand-0option ofxargs. This allows processing files with any allowed characters in names (spaces, new lines etc.). (However I prefer-exec.)There’s an
icommand to insert a line insed, it is better to use it instead ofs/^/...\n/. It makes code more readable (if we can talk about readability ofsedcode, huh).If you want to split a delimiter separated line and print some field, you need
cut. Keepawkfor more complicated tasks.Depends on the delimiter too! For anyone else reading this, sed accepts many kinds of delimiters.
sed "s@thing@thing2@g" file.txtis valid. I use this sometimes when parsing/replacing text with lots of slashes (like directory lists) so I can avoid escaping a ton of stuff.