Quoth Jacob Meuser, on Wed, 4 May 2005 19:17:10 -0700: > those are the tools I use when I need them. as the others said, > there's always sed and perl.
Thanks for the information. I'm still not sure about the newline at EOF, but I did this for the trailing whitespace problem: #! /bin/bash declare files=$* if test -z "$files" then files=`find /my/sourcecode/Java/ -name "*.java"` fi if test "$files" then sed -r -i s/[\ \ ]*$//g $files echo Trailing whitespace removed from `echo $files | wc -w` files. fi The whitespace in the sed expression is just a literal space and a tab char, of course. As for the newlines, I'm thinking our CVS server has been stripping those off, so without reconfiguring CVS, it's probably a losing battle anyway. Grazie a tutti, --Jason -- "The power to untie is stronger than the power to tie." Well, yeah, otherwise my shoes would tie themselves. _______________________________________________ EUGLUG mailing list euglug@euglug.org http://www.euglug.org/mailman/listinfo/euglug
