Closed vizzale closed 1 year ago
What OS are you running, and what setting is File System Watcher
configured with? Open Settings → Core and look for a field that looks like this:
The issue you're describing sounds like it might be an issue with Atom's ability to dispatch or respond to filesystem events (such as deleting or creating a file). Creating a new .editorconfig
file should be all it takes to get the authored settings applied to project files. That is, this shouldn't be happening:
I know that changing the settings of the file these do not apply to existing files. But by opening these files should the system not at least notify me if there are inconsistencies with the
.editorconfig
file?
Hello
I have same/similar issue with an existing project
this is my editorconfig dot file
# https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties
root = true
[*]
indent_style = space
indent_size = 4
tab_width = 4
trim_trailing_whitespace = true
end_of_line = lf
charset = utf-8
insert_final_newline = true
[*.css]
block_comment_start = /*
block_comment = *
block_comment_end = */
[*.styl]
block_comment_start = //
max_line_length = 80
[*.md]
trim_trailing_whitespace = false
block_comment_start = <!--
block_comment_end = -->
Creating a new .editorconfig file should be all it takes to get the authored settings applied to project files. That is, this shouldn't be happening:
I deleted and recreated the file with the changes below
indent_size = 2
tab_width = 2
And rerun editor config fix file or via eclint nothing happens and editor config happily reports nothing changed.
If I change the indent style to tabs it changes everything to tabs but keeps the 4 and not 2, I tried similar workarounds to no avail.
OS is Windows 10 2004 pro workstation Atom 1.58.0 64 bit Atom is using Native Operating system APi's se in core.
Thanks in advance for your work on this project.
@Alhadis thoughts? on this. Im trying to avoid to create a whole new project to workaround this.
Closing as Atom is abandoned.
First of all thank you for your work.
I have two doubts, I still don't know if they are problems with the package or if it depends on my incorrect use. 1) If I create an .editorconfig file inside a project folder with files it already exists I know that changing the settings of the file these do not apply to existing files. But by opening these files should the system not at least notify me if there are inconsistencies with the .editorconfig file? 2) The second doubt is the following. I created an .editorconfig file, placed it inside a project folder, did some tests and I deleted the folder. Then I created a new folder and launched the "EditorConfig: Generate Config" command but the message "An .editorconfig file already exists in your project root." appears. Why does this error appear if I previously deleted the folder that contained it?
Thanks in advance for the help.
Involved .editorconfig-files
Installed packages