Bug 330843 - [PATCH] Support .editorconfig config files
Summary: [PATCH] Support .editorconfig config files
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 09:06 UTC by mokush
Modified: 2018-11-29 09:13 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mokush 2014-02-06 09:06:18 UTC
.editorconfig files want to be a unified config standard, per folder, for editor configuration settings like indentation type, charset, etc.

Since Kate already supports some of these configs in a similar way - trough .kateconfig files, it would be great if it could also parse .editorconfig files, and be compatible with other editors as well.

http://editorconfig.org/
Comment 1 Mathieu Jobin 2014-04-15 10:08:36 UTC
interesting
Comment 2 Daniel Zeiter 2015-03-25 20:27:56 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Philipp A. 2017-02-10 09:33:01 UTC
yes, this would be amazing.

this would have to interact with kate’s own .kateproject files.

at least PyCharm lets .editorconfig override its own settings and displays an info message, maybe we should follow suit:

I also think .kateproject isn’t very discoverable, and the message should be specific and mention both filenames or even paths, like so:

> Settings in ~/dev/myproj/.kateproject have been overridden by ~/dev/myproj/src/.editorconfig: indent-width, enforce-trailing-newlines.
> 
> Consider consolidating the settings in the .editorconfig
Comment 4 Dominik Haumann 2017-02-12 15:39:24 UTC
Proposed patch: https://phabricator.kde.org/D4537
Comment 5 mokush 2018-11-29 09:13:08 UTC
This is implemented in the latest version. Setting it as resolved.