Easier: install Pipe Viewer (http://www.ivarch.com/programs/pv.shtml) and, instead of
cp a b
run pv < a > b cp a b
run pv < a > b*Hmmm, I can't back up my own predictions:
cp huge blah 0.11s user 7.94s system 6% cpu 2:12.54 total
pv < huge > something 0.12s user 8.10s system 7% cpu 1:54.86 total #!/usr/bin/env python
from sys import argv
from subprocess import Popen
copy_from = open(argv[-2],'r')
copy_to = open(argv[-1],'w')
Popen("pv", stdin=copy_from, stdout=copy_to)
copy_from.close()
copy_to.close()
Just alias cp to it in Bash.Still, nice pointer to the pv tool, which I hadn't heard of.
Still still, the linked awk snipped is awfully clever and more fun to read.
My team and I use a hack which overrides cd and as well as calling builtin cd it sources a script if it exists from cwd. This means you can get the exact enviroment you need for that working copy of a project.
cp() { pv < $1 > $2; }
(Or name the function something else if you want regular cp still available.) sudo port install pv
"just works" :-) (Well, assuming you use MacPorts anyway.)