Closed glennpratt closed 7 years ago
Ping @florianb
Thanks @glennpratt - this is again one of the interpretable properties of editorconfig.
The current implementation imitates the behaviour of Atom's whitespace package. You probably agree that I am careful in changing behaviour due to single user requests.
In my opinion the editorconfig-standard leaves far too much room for interpretations. I will think about if this property should behave differently and which behaviour is common.
Until this is changed you can disable this property by setting it to an invalid value or commenting it out.
I am sorry I don't have a better answer yet..
Thanks! That workaround would not have occurred to me. I wonder if a 'disabled' flag is what's needed in the editorconfig-standard?
For others, something like this worked for me if you need newlines in certain files (or in a subdirectory):
root = true
[*]
insert_final_newline = true
trim_trailing_whitespace = true
[*.txt]
insert_final_newline = invalid_value_to_disable_this
editorconfig/editorconfig#282
Closing this as the issue seems to lie with the standard. See link above.
If manynewlines.txt contains many final new lines, it is reduced to one or zero based on the value of
insert_final_newline
.If
insert_final_newline
is false, I would prefer nothing changes.Involved .editorconfig-files
Directory structure
Installed packages