Problems with Line-Endings

[feanaro88]

Expected Behavior

We are a small Team of Devs with different OS (Linux, Mac, Windows) so we all have systems with different line endings.
Since we switched from 0.47.1 to ktlint-cli 1.3.0 the tool touches the line endings. I have searched for an option that just says: keep the line-endings as they are. But only the following are supported in the .editorconfig:
end_of_line = lf
end_of_line = crlf
end_of_line = cr

So what we have done is to create an .editorconfig_win/.editorconfig (as default for linux) /.editorconfig_mac with identical rulesets but differet eol.

The next problem occured: It seems if i run ktlint and if it finds any ".editorconfig" the settings of this file overwrites any passed editorconfig argument.
=>

If i run
ktlint --editorconfig=.editorconfig_win -F
on my windows machine, all the files get LF ending instead of CRLF.

As a workaround every Dev just sets temporaly the correct line ending in the .editorconfig for formatting. This is a risk, they have to take care not to check in their eol-setting...

1. We need a "end_of_line = keep it " option
2. If a default .editorconfig file is found in the CWD it should not overwrite settings of a argument-passed editorconfig

Your Environment

• Version of ktlint used: 1.3.0
• Relevant parts of the .editorconfig settings: end_of_line = cr/crlf/lf
• Operating System and version: Multiple Windows 11/10, Ubuntu 22.4 and some macos quatsch (i dont like macos :))

[paul-dingemans]

Duplicate of #2747