dandv wrote:

martin wrote:

Are you editing local files or what?

Yes, for example before transferring them.

Would be worth mentioning that initialy.
Well you are editing file on Windows, so WinSCP uses CRLF.

martin wrote:

Are you editing local files or what?

Yes, for example before transferring them.

dandv wrote:

The server protocol is SFTP with "Allow SCP fallback", but no transfer is ever taking place.

Are you editing local files or what?

The server protocol is SFTP with "Allow SCP fallback", but no transfer is ever taking place.

dandv wrote:

I'm encountering the same bug in 4.1.8. The internal editor will save the newlines in a file as CRLFs, no matter what. This does not involve any transfers. Simply edit a LF-separated file with the built-in editor, then save it. Notice that the linbreaks have been converted to CR/LF.

It does not matter, but I had the end-of-line characters set to "LF" in my Server Environment preferences.

What protocol?

I'm encountering the same bug in 4.1.8. The internal editor will save the newlines in a file as CRLFs, no matter what. This does not involve any transfers. Simply edit a LF-separated file with the built-in editor, then save it. Notice that the linbreaks have been converted to CR/LF.

It does not matter, but I had the end-of-line characters set to "LF" in my Server Environment preferences.

You may have changed default transfer mode in WinSCP.

martin wrote:

Only if you configure it to do so.

Sorry. I meant 4.1.7
I can't find where this is configured. I looked at every option I can see.

Never mind. I see in the docs;

The internal editor supports only Windows-format text files.

So I guess I will need to configure an external editor. But I don't remember having this problem until recently. I have been using WinSCP since the early 3.xx versions.

Only if you configure it to do so.

Editor in 3.1.7 changes edited files from unix LF's to dos CR/LF.

After editing files you have to run dos2unix on them