it’d be nice if I could cryptcheck a cache. even if all the command does is ignore the cache system entirely.
So right now I’m running a lot of commands
rclone copy -v --fast-list --drive-chunk-size 128M “localdirectory\localfile” “namecachecrypt:localdirectory”
then I run
rclone cryptcheck -v --fast-list --drive-chunk-size 128M “localdirectory\localfile” “namecrypt:localdirectory”
why? because running cryptcheck on a cache simply does not work at all ever.
now if it’s impossible to use a cache to run a cryptcheck, okay, fine, but i’d still like the command to know that. having to edit the name of my remote in all my command line commands is quite annoying.
there’s really no reason it has to work the way it currently does, since a cryptcheck makes 0 remote changes it doesn’t threaten the freshness of a cache at all.
Also while I’m at it. my cryptcheck usually uses --one-way in these situations, because I just want to check my most recent choices. I’d like --one-way as a flag to work for the copy command. It wouldn’t do anything, but why does it have to give me an error and refuse to run the command? The copy command is naturally always --one-way as such I’d like it to be the case that if you try to run the copy command with the --one-way flag the --one-way flag just has no effect. That means I can run rclone copy --one-way “source” “target” then run rclone cryptcheck --one-way “source” “target” and the commands are more similar and easier to type.
Personally I can’t see any harm in this, but, well, maybe I’m being shortsighted.