Closed gsklee closed 7 years ago
Hi @gsklee - thanks for getting in touch!
Unfortunately i am missing your directory-structure and can't reproduce the error.
I can only guess that your markdown-files may lie in subdirectories where the *.md
-glob isn't enough to catch them. If you want to catch markdown files in subdirectories, try **/*.md
instead. If not, please provide a listing of your directory structure.
I couldn't reproduce this issue with the following directory structure:
$ tree -a .
.
├── directory
│ └── file2.md
├── .editorconfig
└── file1.md
1 directory, 3 files
Both file1.md
and file2.md
have the following content (there are 4 spaces behind Line with trailing whitespace
) :
# Title
Line with trailing whitespace
.editorconfig
file content is identical to the one @gsklee provided.
When I hit Ctrl+S, spaces at the end of the line Line with trailing whitespace
remain unchanged.
Versions:
$ atom --version
Atom : 1.13.0
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
$ apm list | grep editorconfig
├── editorconfig@2.2.0
It's the README.md
, which is file1.md
in @orgkhnargh's example, so @florianb's hypothesis doesn't apply.
Above is my configs for the whitespace
package, which might be relevant.
Thanks @orgkhnargh! 🎁
@gsklee the whitespace package is known for interfering the usage of atom-editorconfig. Did you try disabling the whitespace-package?
Also try to get the file status of your README.md (with invoking the EditorConfig: Show State
command while the README is opened) and what is the trim_trailing_whitespace-property saying there?
I close this issue due to missing response -- feel free to come back if you think this issue needs more attention.
Thank you for contribution! 💝
Problem
Trailing whitespaces are still being auto-trimmed whenever I hit Cmd-S inside a Markdown file, even though I have the following config:
Involved .editorconfig-files
Directory structure
Installed packages