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
- Docker, SELinux, Consul, Registrator
(Wednesday, 04. 29. 2015 – No Comments) - ZFS performance on FreeBSD
(Tuesday, 09. 16. 2014 – No Comments) - Controlling Exim SMTP behaviour from Dovecot password data
(Wednesday, 09. 3. 2014 – No Comments) - Heartbleed OpenSSL vulnerability
(Tuesday, 04. 8. 2014 – No Comments) 
Archives
- April 2015
 - September 2014
 - April 2014
 - September 2013
 - August 2013
 - March 2013
 - April 2012
 - March 2012
 - September 2011
 - June 2011
 - February 2011
 - January 2011
 - October 2010
 - September 2010
 - February 2010
 - September 2009
 - August 2009
 - January 2009
 - September 2008
 - August 2008
 - July 2008
 - May 2008
 - April 2008
 - February 2008
 - January 2008
 - November 2007
 - October 2007
 - September 2007
 - August 2007
 - December 2006
 - November 2006
 - August 2006
 - June 2006
 - May 2006
 - March 2006
 - February 2006
 - January 2006
 - December 2005
 - November 2005
 - October 2005