On Fri, Sep 21, 2018 at 5:54 PM Nate Graham wrote:
>
>
>
> On 09/21/2018 04:40 AM, Tomaz Canabrava wrote:
> > Hello fellows.
> >
> > In kde software we strive to be inclusive, that means that we don't
> > enforce a coding style in every new project, nor do we adapt to newer
> > styles on old softw
On 09/21/2018 04:40 AM, Tomaz Canabrava wrote:
Hello fellows.
In kde software we strive to be inclusive, that means that we don't
enforce a coding style in every new project, nor do we adapt to newer
styles on old software. This can create a bit of problems when we edit
two projects at the
This is a great idea! I'll see about making this the projects I'm working
on.
On Fri, Sep 21, 2018, 7:17 AM Tomaz Canabrava wrote:
>
>
> On Fri, Sep 21, 2018 at 12:58 PM Kai Uwe Broulik
> wrote:
>
>> Hi,
>>
>> I would suggest to have Kalgebra follow KDE Frameworks coding style then
>> which use
On Fri, Sep 21, 2018 at 12:58 PM Kai Uwe Broulik
wrote:
> Hi,
>
> I would suggest to have Kalgebra follow KDE Frameworks coding style then
> which uses four spaces and no tabs, or add an editorconfig there.
>
> I have hardly encountered any KDE code that uses tabs, so this isn't a
> widespread is
Hi,
I would suggest to have Kalgebra follow KDE Frameworks coding style then
which uses four spaces and no tabs, or add an editorconfig there.
I have hardly encountered any KDE code that uses tabs, so this isn't a
widespread issue imho. Placement of braces and asterisks might be
inconsistent
Hello fellows.
In kde software we strive to be inclusive, that means that we don't enforce
a coding style in every new project, nor do we adapt to newer styles on old
software. This can create a bit of problems when we edit two projects at
the same time.
For instance, on the KDE-Edu module, we ca
