Getting Style
Sven Brauch
svenbrauch at googlemail.com
Sat Apr 21 17:03:09 UTC 2012
Hi,
okay, starting from that configuration:
1) Do you all really want that "foo( 3 )" spacing style? I find it
ugly and a pain to type, too.
2) I'd suggest to force moving the & and * chars to the type
(untouched currently).
3) isn't the alignment issue david raised solved by the "indent parent
nl" option?
4) I'd turn on "add space after comment start", but that's not important.
5) the current setup indents a closing bracket on another line
(function call), is this intended? I think it's ugly.
Greetings
Am 21. April 2012 18:40 schrieb David Nolden
<david.nolden.kdevelop at art-master.de>:
> I suggest to take format.config.uncrustify.4_spaces and propose
> _changes_, so that we have clear and isolated options we can discuss
> about. The whole parameter-set is simply too large to discuss it at
> the same time, because you can hardly demonstrate all effects in a
> single example snippet.
>
> In my experience, apart from some minor parser glitches (it wrongly
> formats some template code where type-information is required to
> interpret the code), the main problem of uncrustify is with manually
> aligned code, which it usually breaks, for example something like:
> function( "arg1",
> "arg2",
> "arg3" )
> becomes:
> function( "arg1",
> "arg2",
> "arg3" )
>
> Which actually is something I might get used to.
>
> --
> 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