-
-
Notifications
You must be signed in to change notification settings - Fork 80
Fallback to ~/.atom/.editorconfig #159
Comments
Hi @svoop - thanks for your suggestion. You are absolutely right, currently this case is not properly handled by this package. We won't support a "user"-based default But to get back to your point, i would like to introduce a automated "deactivation" of packages in the fututure. But since this is a pretty intrusive procedure this is something which must be done pretty careful. So unless this is solved in a satisfying way, we enabled a notification about potential misbehavior. I hope this explains why we are at the current state of functionality. ☕️ |
Indeed, and with an opt-out fallback to the current behaviour maybe. I'd opt-in though 😄 |
I am aware of your point. Sindre Sorhus advised me rightly to stick to a smart solution rather than introducing configuration-options. Give me some more time to think about how this could be solved the smart way. |
Currently, any EditorConfig setting that's As for the |
Editorconfig clashes e.g. with widely used Whitespace. However, disabling Whitespace is not really an option because you may use Atom in places where no
.editorconfig
is defined – most notably when using remote-atom.How about adding a fallback to
~/.atom/.editorconfig
if no.editorconfig
is found down the current path? This way, Whitespace could be dropped in favour of Editorconfig everywhere.The text was updated successfully, but these errors were encountered: