On 5 May 2009, at 11:57, Christiaan Hofman wrote:
This is a very common practice whose rationale is that white spaces are a distraction in diffs. By forbidding them, only those lines with meaningful differences are displayed in diffs.Maybe this may make sense when you're managing files you write yourself. Otherwise, IMHO it makes no sense to do this.
I am working on a large scientific project which contains source code (Python and C++ files) as well as LaTeX files and Bibtex files for documenting the science and math bits. I agree with you that what makes sense for the former does not for the latter and that I should try to make my code version system (git) treat source code and LaTeX stuff differently but that would force me to swim upstream against git's default.
Well, the usual cultural conflicts between two tools coming from different worlds. Never mind. I can hack Bibdesk sourcecode to my liking at least.
Thanks for making Bibdesk open-source. And thanks for a great program and for your time.
Luc Bourhis Computer Scientist Chemical Crystallography Laboratory University of Durham, UK
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
