Updates to .editorconfig don't update open files

[erikdonohoo]

Files need to be closed and reopened for changes to the .editorconfig to be noticed.

The file should be watched and then refresh any currently open files to show the changes.

[travi]

+1

[mstn]

+1

[xlaywan]

+1

[sindresorhus]

Yes, that would be nice, but I'm not aware of any way to do that in Atom. Though I would love to be proven wrong.

[erikdonohoo]

I will have to look. But I know it is done in the atom jshint package. They watch for changes to any .jshintrc file and update the hinting.

[sindresorhus]

Sure. PR welcome.

[cemrich]

There is a fs.watch() function that could be used.
The problem is we don't know the exact files the config rules are parsed from. In most cases it will be .editorconfig on root level but there could be more config files in subdirectories as well.
Searching for this files could be expensive (however, that's just an assumption) - especially when handling deeply nested node_modules directories.

[florianb]

We could try to watch all involved files, if one file changes the config is resembled and set.

[florianb]

This feature will be implemented with the next (and first) feature-milestone. I will close this issue in favor of the more technical discussion in #85 - please feel free to follow up and participate!

Thank you all for contributing! 💝