To propose changes, please open an issue at theissue tracker. Then, after short discussion, we will start reviewing the format change following the rules describedhere to be voted by current board members.

Existing files are not reformatted by the plugin (only newly input lines are formatted in the format given in the.editorconfig files) but if you would like to use a separate tool to do this then see the next question.

Yes! You might like to try:

• editorconfig-tools
• eclint
• editorconfig-cf
• editorconfig-maven-plugin
• editorconfig-gradle-plugin
• editorconfig-checker

You could use one of these tools to tidy up existing code in a repository, and then set it torun as a continuous integration test to ensure code stays tidy in the future, but please note that none of these tools work perfectly at the moment. In addition, aGitHub Action exists to check and enforce project style against a top-level.editorconfig usingeclint.

It is likely to happen on macOS with Vim and Python installed using Homebrew. It usually happens after a Python upgrade, at which time the old Vim installation does not recognize the new Python installation. To fix it, runbrew reinstall vim orbrew reinstall macvim. If it didn't help, try to recompile Vim locally runningbrew reinstall vim --with-custom-python orbrew reinstall macvim --with-custom-python. For more info, checkbrew info vim /brew info macvim.

Since EditorConfig core executables are usually not supposed to be called by humans from command line, we did not support relative paths for simplicity across all implementations of EditorConfig cores. However, if you really need to call it from the command line (e.g., for debugging), you can use the following way to call it on a POSIX system, if therealpath utility is available on your system:

editorconfig "$(realpath my-file.ext)"

or use the following command, ifrealpath is unavailable:

editorconfig "$(pwd)/my-file.ext"