Andrew Straw wrote: > Eric Firing wrote: >> Yes, I understand, and I am sorry--but I hope it is one-time pain to >> avoid continuing pin-pricks. If svn ignored trailing whitespace, then >> there would be no problem; I could continue to use an editor that >> removes it, and you could continue to use editors that gratuitously add >> it, and usually it would make no difference. This is not the case, >> however. As it is now, if a file comes into svn without any trailing >> whitespace, and one of you loads it up, maybe makes a trivial change >> after running your cursor through it, and saves it--it will end up with >> a big changeset--lots of trailing whitespace. This is just plain bad. >> All downside, no upside. >> > FWIW, you can get svn diff to ignore (trailing whitespace) -- by not > using svn diff. > > svn diff --diff-cmd diff -x -uw path/to/file.py
Almost. Quotes are needed for the diff options: svn diff -x '-uw' path/to/file.py This is useful, but doesn't help with the problem of noise in changesets. > > With apologies for previously hijacking your thread into an emacs > configure-a-thon, :) No problem--everyone but me uses emacs or vi, it seems, so figuring out how to configure emacs is what it takes to address the problem. Eric ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
