Inevitable evil: developer drops off a load of content with DOS line endings, flutzing up editor screens with ^M.
$ find /some/path -type f -exec perl -pi -e'y/\015//d;' \{\} \;
It’d be nicer to used xargs(1) instead of find(1)’s own -exec flag - way more efficient. However, chances are that if there’s borked line endings in a file tree then there’s probably also filenames with whitespace…
Not editing binary files would also be a bonus!
Leave a Reply
Recent articles
- MySQL replication health
(Tuesday, 09. 30. 2008 – No Comments) - Firewalls
(Friday, 09. 5. 2008 – No Comments) - Using Single Sign-On To Integrate Ning With An External Site
(Wednesday, 08. 20. 2008 – No Comments) - High Availability Rails Cluster
(Tuesday, 08. 19. 2008 – No Comments)