Support basic .editorconfig options

2 votes

Many IDEs and tools support .editorconfig (https://editorconfig.org/) files, either directly or through popular add-ons/extensions. The .editorconfig file includes basic options to control file encoding/character sets, whitespace preferences, and more. The built-in GitKraken editor does not appear to support or respect the .editorconfig files' options. For example, one of my .editorconfig files sets the file encoding for `.cs` and `.sln` files to UTF-8-BOM, matching the expectations of Visual Studio.

Currently, it appears possible to set a repo-specific default encoding in GitKraken's preferences. However, this is less than ideal as I really only want UTF-8-BOM for the `.cs` and `.sln` files with others using UTF-8 without the BOM.

GitKraken supporting the "universal properties" defined in .editorconfig files (https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties) would improve compatibility with all of my other, existing tools and prevent some annoying conflicts.

Submitted for Review Suggested by: Kyle Dodson (29 Jun, '24) • Upvoted: 06 Dec, '25 • Comments: 0