The problem is with slashes: your variable contains them and the final command will be something like sed “s/string/path/to/something/g”, containing way too many slashes. Since sed can take any char as delimiter (without having to declare the new delimiter), you can try using another one that doesn’t appear in your replacement string: replacement=”/my/path” sed –expression … Read more
I’m surprised nobody has mentioned the -exec argument to find, which is intended for this type of use-case, although it will start a process for each matching file name: find . -type f -name ‘xa*’ -exec sed -i ‘s/asd/dsg/g’ {} \; Alternatively, one could use xargs, which will invoke fewer processes: find . -type f … Read more
sed is a stream editor. It works with streams of characters on a per-line basis. It has a primitive programming language that includes goto-style loops and simple conditionals (in addition to pattern matching and address matching). There are essentially only two “variables”: pattern space and hold space. Readability of scripts can be difficult. Mathematical operations … Read more
sed is intended to be used on line-based input. Although it can do what you need. A better option here is to use the tr command as follows: tr ‘\n’ ‘ ‘ < input_filename or remove the newline characters entirely: tr -d ‘\n’ < input.txt > output.txt or if you have the GNU version (with … Read more