The problem is that when I run them, nothing happens. The real problem is that people have been pasting stuff from Beej for years without understanding it. That’s why I don’t really like that guide; it gives large blocks of code without really explaining them in detail. You’re not reading anything and not sending anything; … Read more
In a shell, you can do: sed ‘s/ /\ /g’ hitting the enter key after the backslash to insert a newline.
Doing socket I/O efficiently has been solved with kqueue, epoll, IO completion ports and the likes. Doing asynchronous file I/O is sort of a late comer (apart from windows’ overlapped I/O and solaris early support for posix AIO). If you’re looking for doing socket I/O, you’re probably better off using one of the above mechanisms. … Read more
Since only the shell knows how to run shell functions, you have to run a shell to run a function. You also need to mark your function for export with export -f, otherwise the subshell won’t inherit them: export -f dosomething find . -exec bash -c ‘dosomething “$0″‘ {} \;
With BSD/macOS sed, to use a newline in the replacement string of an s function call, you must use an \-escaped actual newline – escape sequence \n is not supported there (unlike in the regex part of the call). Either: simply insert an actual newline: sed -i ” ‘s/\\n/\ /g’ test1.txt Or: use an ANSI … Read more
If you really want to just use sed -i the ‘easy’ way, the following DOES work on both GNU and BSD/Mac sed: sed -i.bak ‘s/foo/bar/’ filename Note the lack of space and the dot. Proof: # GNU sed % sed –version | head -1 GNU sed version 4.2.1 % echo ‘foo’ > file % sed … Read more