WinSCP 5.1.x: Custom Commands not monitoring changes

Hello,

We are unable to get the Custom Commands working with SourceGear DiffMerge.

This help document indicates that there are four types, including "Special" but my version 5.1.2 only has Local and Remote.
When I use Local and save the file in DiffMerge, it gets saved to disk but it is not uploaded to the remote server.

The four types of Custom Commands are found here,
https://winscp.net/eng/docs/custom_command

It was last updated last year, is it perhaps outdated and two options have been removed?

https://winscp.net/eng/docs/custom_command :

Local commands that are executed on the local machine with remote files downloaded to a temporary folder. It makes no sense for the command to modify the files, because they are not uploaded back after the command finishes. You must have remote files selected first in order to execute the command.

Also see
https://winscp.net/tracker/169

The four types of Custom Commands are found here,
https://winscp.net/eng/docs/custom_command

It was last updated last year, is it perhaps outdated and two options have been removed?

There are conceptual four types. What type your command is depends on the patterns used in the command.


Btw, what for your donation!

martin wrote:

https://winscp.net/eng/docs/custom_command :

Local commands that are executed on the local machine with remote files downloaded to a temporary folder. It makes no sense for the command to modify the files, because they are not uploaded back after the command finishes. You must have remote files selected first in order to execute the command.

Thanks for the reply. I read that, so it is correct that all Diff examples are just meant to show differences and not really apply them?
For me it makes alot of sense that it treats these downloaded files the way it does when you edit them. At least with the option to make them editable, so it monitors changes... but I guess, that's what Bug Tracker 169 shows, that it is a feature not implemented yet?

IsaackRasmussen wrote:

Bug Tracker 169 shows, that it is a feature not implemented yet?

Correct.