Re: Proposal, Adopt .editorconfig in every project
- Date: Wed, 31 Oct 2018 09:40:24 +0100
- From: Tomaz Canabrava <tcanabrava@xxxxxxx>
- Subject: Re: Proposal, Adopt .editorconfig in every project
On Fri, Sep 21, 2018 at 5:54 PM Nate Graham <nate@xxxxxxx> 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 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 can look at kalgebra, and it
> > uses indentation of 4 space, while in blinken it uses a single tab
> > indentation. Curently if I open kalgebra in any editor based on
> > ktexteditor I will need to go to settings, change the tab behavior, edit
> > kalgebra files, then go to settings, change tab behavior again, edit
> > blinken files. That's too easy to miss. (I actualy missed and had to fix
> > a review because of tabs / spaces).
> Related, and another potential solution to the issue (at least for Kate
> users): https://bugs.kde.org/show_bug.cgi?id=109338
This is nice but no solution, as we can't force people to use Kate.