I would prefer Eclipse Build In, which is what we use for CDT (tabs and
line max 120), but I saw bunch commit like
"Changing tabs into spaces to comply with sonar", so I assumed if some-what
important.

On Fri, Nov 27, 2015 at 10:10 AM, Roland Grunberg <rgrun...@redhat.com>
wrote:

> > Hi Guys! Decided to join mailing list since I am working on valgrind
> plugin
> > now.
> > I noticed (in commit history) that you trying to use spaces instead of
> tabs
> > but I cannot
> > find your other rules for code formatting nor format.xml I can import
> > linuxtools projects.
> > Is it defined somewhere?
>
> I would have thought the default is tabs given that's what the 'Eclipse
> Built-in' formatter does. It's always possible to enable project specific
> formatters and push the corresponding .settings/ files so that all Eclipse
> IDE users follow that standard.
>
> I can't find any rules regarding this so my guess is we've always just gone
> by what the project has already defined.
>
>
> Cheers,
> --
> Roland Grunberg
>
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Reply via email to