Eh, to each their own, and that doesn't explain what happens that makes vi screw up like that.

For me, vi does what I need done, and I am rather minimalistic in my utilities (though based on my conceptions of what I may conceivably some day need and not have internet access to install, this leads to what some might view as the opposite of that).

Anyway, I'm having a wonderful mass of error outputs after copying the script directly from that page, so type to go through the code manually.

line 1: #!/usr/bin/env: not found
(Okay - the original code uses /usr/bin/env python - A few posts up butler uses /usr/bin/python - will try that.)
line 29-33 (same error): import: not found
(Sigh... this means I have to dig up the stuff it's trying to import, doesn't it? Or is it going to be found when/if the code is able to find the right interpreter?)
Line 35: maxdownloads: not found
Line 36: TM: not found
Line 37: cpid: not found
Line 38: compressed: not found
Line 42: syntax error: "(" unexpected
(I'm just gonna suppose that all of these are byproducts of it not finding the python interpreter courtesy of me not checking to make sure it pointed to the right thing.)

Actually, I'll save you the trouble of rereading when I edit this, sine I just tested it with just the first line fixed, and at least "woof -h" works. I leave the above post fragments up for posterity, in case another python+linux newb on here is able to see this if they're having a similar bug, and see how it got solved.

Now, I didn't want to fiddle with .profile making and/or $PATH, so I just put the woof into my /usr/bin directory.