kdelibs will have coding style conventions. In general. this is not a bad idea. Our 45528 slocs in KatePart all use a consistent indent-width of 2 spaces. Changing this does not really make sense – ok, if svn praise -w (sure, we never need svn blame in our code finally works, we can discuss this again.
In other words: How “consistent” will kdelibs get with this new conventions? The interesting part of Zack’s mail is
[…] No exceptions. Either everything or nothing
While everything would really be cool, in truth it’s not possible to achieve, is it? We will have exceptions or rather violations, I’m pretty sure
Some developers already start adding katepart modelines to their souce code. For those who don’t know yet: You also can simply use a single .kateconfig file, which is the equivalent to emacs dir config files. You just have to make sure to set the search depth for a .kateconfig file to – let’s say – 3. Do this in
Settings > Configure Kate… > Open/Save