consistency wrote:if i create a new file with shift + f4 the file will always created with ANSI and with Windows Line endings, which is quite outdated.
No, it just creates an empty file.
It exclusively
depends on your editor how things are treated, in case of an empty (zero byte) file.
You can select e.g.
Notepad2 as the default editor:
Options ->
Edit/View ->
Editor for F4
and insert e.g.
Code: Select all
%COMMANDER_PATH%\tools\notepad2\Notepad2.exe /utf8 /crlf
This way empty/created files will always be treated as UTF-8 and CRLF,
and existing files will still be recognized and opened in their correct encoding (Unicode detection).
Use /lf switch for Unix line endings, and so on.
I'm sure that there are also similar command line switches for
Notepad++.
While I agree that TC could (optionally) insert an Unicode BOM for newly created files,
pre-selecting the line endings is not a thing that makes sense, because you'd need to insert empty lines for that,
in order to make the editor recognize what endings should be used.