On Wed, 2009-10-21 at 18:47 +0200, Ramon Ribó wrote: > I also like beautiful things and hate ugly things. But life is > sometimes difficult and it is better to fix problems instead > of workaround them.
If there is, in fact, a problem. Obviously I can't tell you you don't have a problem if you think you do, but the two examples you gave, to me, only demonstrate that line endings are meaningful and should be treated as a genuine part of the data rather than something ancillary that can be automatically reconstructed. I.e., the TCL script should *always* have unix line endings--there's no good reason for it to be otherwise. And the README, if it's meant to be read by non-expert Windows and Linux users alike, should *always* have Windows line endings. So this is still a non-problem to me, and obviously that's going to color my interest in a "solution", but... > fossil settings read-write-filter my_proc Although conceptually more elegant, it looks to me like this would require my_proc to be invoked on each file in the repository whenever I run `fossil status`. (Well, it wouldn't have to be invoked *for me*, since I wouldn't use the feature. But the presence of the feature and examples might encourage people to think that automatic line ending translation was a good idea, and then it would really start to suck for them once they have a substantial number of files in their project.) -- Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
