Re: Local files that are not empty, show as empty in VSCode when opened through WinSCP on Linux
Isn't the problem that WinSCP runs the VSCode with Windows-style path to the edited file, which Linux VSCode does not understand? So it possibly assumes that you want to edit new (non-existing) file.