Not picking up configuration about atom-editorconfig

[rochapablo]

+1

[kaifaust]

Removing the "whitespace" plugin from config.cson and restarting atom solved this for me.

[ezekg]

My config file has been having issues being picked up as well. Does editorconfig require the default whitespace plugin to be enabled?

[ismay]

My config file has been having issues being picked up as well.

Same problem here, for example, when saving a .js file in version 0.208.0, editorconfig does not trim trailing whitespace with the following config:

# EditorConfig helps developers define and maintain consistent
# coding styles between different editors and IDEs
# editorconfig.org

root = true

[*]
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
indent_style = space
indent_size = 2

[*.js]
indent_style = space
indent_size = 2

When I add some trailing whitespace and move my cursor (by pressing down or up arrow key) it clears all whitespace correctly on save. But when I add trailing whitespace, and don't move my cursor away after pressing spacebar, then it doesn't remove the trailing whitespace.

---

edit: this is because of the core whitespace package, which was set to ignore whitespace on the current line.

[lucasmotta]

+1

[brandonb927]

Ok I thought I was going crazy when on load It looks like Atom 1.0 is going to use my .editorconfig, however after about 2 seconds it reverts back to the Atom settings config and not using my projects .editorconfig.

+1 on this issue

[bobrocke]

@brandonb927 This has proven to be a difficult mess. And I know the Atom folks have struggles with the "right" solution in the case of the file content, .editorconfig, and Atom's preferences differing. I don't think I've worked out how the conflict is handled within Atom.

If you hand edit your file to make it conform to your .editorconfig settings, will Atom respect that on load even if Atom's preferences are different?

[brandonb927]

I'm not sure what you mean by "hand edit"? Do you mean that I should just edit the cson file manually to have it reflect my .editorconfig settings?

[bobrocke]

Yes.

[brandonb927]

That... is not ideal :) I have an editorconfig in many projects I work on daily, switching between them frequently too. You're saying I should manually edit the Atom config whenever I switch then?

[bobrocke]

No. I'm saying that Atom does not seem to handle .editorconfig, it's preferences, and what it finds in a file well if they don't all match up. I was suggesting a way to fix that for one file - make that file match .editorconfig and see if that "sticks."

[brandonb927]

Ah, simple misunderstanding. I'll try that and see if it works.

[bobrocke]

@lee-dohn has written up a bunch on the topic.

[nfantone]

+1 on this.

I have absolutely no idea on how this package works, but it sure does not apply my .editorconfig settings. What am I supposed to do? Autoindent? How does this indent my source files, exactly? Is there any kind of magic keyboard shortcut? Does Whitespace need to be disabled?

[gitgrimbo]

Hi,

I deleted the following two lines from C:\Users\xxx\.atom\config.cson and when I restarted Atom my .editorconfig settings seemed match the formatting when I beautify (Ctrl+Alt+B), but not when I edit (auto-indentation isn't correct, for example).

    softTabs: false
    tabLength: 4

[c4milo]

I was having the same problem. Once I re-opened my source file, it picked up my editorconfig settings just fine.

[brandonb927]

Atom seems to be picking up on my config now

[brandonb927]

Hmm I realized that Atom also stopped picking up my config a few releases ago :(

[bux]

Same here.

[marcelombc]

+1

[zebateira]

👍

[nfantone]

Maybe it wasn't such a good idea to close the issue?

[EloB]

+1, re-open this?

[jbatte47]

+1, not working for me

[jaimeschettini]

+1

+1

[matias91]

+1

[garretmh]

+1

[verlok]

+1

[florianb]

@rochapablo: I would really appreciate if you could open a "new" issue with details about your problems.

For anyone else landing here: The atom-editorconfig-plugin is in a stable and mostly tested state and should work as intended.

The editor might behave unexpected if third-party plugins or languages conflict with the editorconfig-settings and/or the file is already malformed according to the editorconfig-rules.

ℹ️ Please open a new issue in that case - we're happy to help.

P.s.: please do not post to this issue. Since the plugin has evolved a bit in the past weeks it is absolutely unlikely that your issue belongs in any way to the reasons why this was opened in the first place.

[noahehall]

this doesnt work

[florianb]

@noahehall: Please read my comment above - if you're facing any issues please open a new issue and consider especially:

The editor might behave unexpected if third-party plugins or languages conflict with the editorconfig-settings and/or the file is already malformed according to the editorconfig-rules.

[hiddentao]

@kaifaust That worked for me too, thanks.