Let's end the formatting mess

Sven Brauch svenbrauch at googlemail.com
Wed Nov 9 18:19:10 UTC 2011

I'd be okay with most things -- assuming that you'd want to apply your
rules to the plugins, too --, but I'd largely prefer 4 spaces over 2.
2 are just too small for me to see properly. I agree with Aleix in
that if you want to use split a lot, limiting line length is the
correct solution, although I find 80 characters a bit outdated (100 is
However the "breaks blame" argument seems like a really good point to
me against reformatting all the files. I'm not sure if that's worth
it. Anyways, you're the experts, so you should decide about that. :)


2011/11/9 David Nolden <david.nolden.kdevelop at art-master.de>:
> 2011/11/9 Aleix Pol <aleixpol at kde.org>:
>> On Wed, Nov 9, 2011 at 4:21 PM, Alexander Dymo <alexander.dymo at gmail.com>
>> wrote:
>> I don't really like the 2 whitespace either, but I wouldn't like to create a
>> flame about that. If we really want to let people to economize their screen
>> space, I'd say use tabs. That way you can configure the editor however you
>> want, however there's people who really hate those.
>> If we want to standarize, I'd say we should adhere to the kdelibs coding
>> style, I don't really like it either, but some compromise will be always
>> present.
> Tabs are the most terrible option, proven many times to simply not work.
> Btw. I never said I insist on 2-space indentation, only that I would
> prefer it. If everyone would tell his preferences in a calm way, we
> could try finding a compromise. I don't see a reason why we should use
> the kdelibs coding style, we should simply orient on what we already
> have and like, and make it consistent.
> Greetings, David
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

More information about the KDevelop-devel mailing list