Re: Synchronization – File not saved via WinMerge comparison
Ok, we will see, if more people ask for this.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Guest
Re: Synchronization – File not saved via WinMerge comparison
So it seems synchronization, in the current implementation, is for file-level changes. For line-level changes, the explorer view is the way to go.
Perhaps "saving line-level changes in synchronization checklist" is worthy of an RFE? This would allow both file- and line-level changes in the same workflow.
Perhaps "saving line-level changes in synchronization checklist" is worthy of an RFE? This would allow both file- and line-level changes in the same workflow.
- martin
Re: Synchronization – File not saved via WinMerge comparison
Indeed, the files are not saved. That's how it works.
- Guest
Synchronization – File not saved via WinMerge comparison
Version:
WinSCP 6.3.2 on Windows 10 22H2
Protocol:
SFTP
Steps:
Expected:
Remote file saved with some changes from Local file.
Actual result:
Remote file not changed – as if nothing has happened.
Saving changes in WinMerge works when comparing files outside of the Synchronization checklist, e.g. in the explorer UI.
WinSCP 6.3.2 on Windows 10 22H2
Protocol:
SFTP
Steps:
- Synchronize (Direction: Remote)
- Compare a file (external comparison tools: WinMerge)
- Copy some changes from Local file to Remote file
- Save Remote file
Expected:
Remote file saved with some changes from Local file.
Actual result:
Remote file not changed – as if nothing has happened.
Saving changes in WinMerge works when comparing files outside of the Synchronization checklist, e.g. in the explorer UI.