Closed tzvetkoff closed 7 years ago
Hi @tzvetkoff - thank you for reporting this.
Unfortunately i am not able to reproduce your described behavior. Could you please post the content of the involved .editoroconfig
-file as well as the output of the EditorConfig: Show State command?
As a first explanation: If the setting is recognized being set to auto
, the default setting from the Editor get's applied as it is being done when the editor is being opened. This is currently done to explicitly reset any changes from the editorconfig. The auto
-setting is fetching the predefined settings from Atom's config and it is also scope-aware.
To reproduce:
.editorconfig
file in itMakefile
What is the output of EditorConfig: Show State
for the makefile?
Here's the output from EditorConfig: Show State
(I couldn't copy it whole, so I uploaded an image):
Thanks - i still can't verify that behavior.
Try disabling "language-autotools" instead.
Yak... It's language-autotools
indeed. They overwrite the grammar definition for Makefile
(as it's based on name, not scope - and change their scope to source.makefile2
)
Will write to their author to fix that.
Sorry for the incorrect report, and thanks for the quick reply!
You are welcome @tzvetkoff! Happy hacking!
The EditorConfig plugin overrides the default editor settings in projects without
.editorconfig
file.The problem resides in
index.js
, more specifically handling settings with valueauto
.Example debug of
yields
to console, when opening a
Makefile
.I'd propose doing nothing when the configured value is set to
auto
, otherwise it breaks general editor features.Directory structure
Makefile contents
Atom scope config
Installed packages