https://bugs.kde.org/show_bug.cgi?id=406617
Bug ID: 406617
Summary: Use .editorconfig and .kateconfig at the same time
Product: kate
Version: unspecified
Platform: unspecified
OS: unspecified
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: part
Assignee: kwrite-bugs-n...@kde.org
Reporter: sniperrifle2...@gmail.com
Target Milestone: ---
I am currently moving from atom to kate and have some difficulty getting the
combination of settings I want for a project. The project uses a .editorconfig
for consistent indentation and other general settings and this works fine.
Unfortunately this does not support connecting a file type to a glob, which
means syntax highlighting does not always work properly (In particular with
templating languages or files with extensions that are otherwise not directly
mappable to their syntax).
So I decided to use a personal .kateconfig file with document variables to set
the syntax. However after that the editorconfig settings were no longer
applied. I did read that KatePart prioritizes .kateconfig files, but I did not
expect the editorconfig to be ignored completely.
So I would like kate to read them both, so I can leverage kate-wildcard
document variables for stuff that editorconfig doesn't handle. I suggest
reading configuration like this (Altered from
https://docs.kde.org/stable5/en/applications/katepart/config-variables.html):
- The global configuration.
- Optional session data.
- The "Filetype" configuration.
> - Properties in .editorconfig. <
- Document variables in .kateconfig.
- Document variables in the document itself.
- Settings made during editing from menu or command line.
NOTE: From a project "I want consistent settings" perspective it would make
more sense to prioritize editorconfig, but from the editor perspective
prioritizing the editor specific configuration makes more sense. It's tricky
because both configurations work at the same logical level.
--
You are receiving this mail because:
You are watching all bug changes.
