--track-renames but AFAIU it works only if the file hasn’t been moved to another folder (it makes sense though, because rclone would have to check the hash of all files in a remote).
I was thinking about an implementation like
rclone multimount --sync-renames --sync-moves GDrive1: GDrive2: GDrive3:
that would perform the rename/move actions on all remotes. If a file didn’t exist for some reason on a remote it would log a NOTICE or WARNING.
What it would do is to execute an action multiple times, each time for a different remote.
I’m not sure if anyone else agrees that this would be a useful feature.
If not then maybe I would suggest an extra flag like
--track-full-renames that it would check the hash of all the files in the destination to track the renames; but I think that would require much time/resources.
I don’t know much about Go language, but to my simple mind it doesn’t seem very difficult to make it repeat a write/move/rename action multiple times on different remotes at the same time.