Wouldn't it be nice to have a 'Save Script As..." function?

[Manu Chao]

Originally Posted by dnanian

Yes, they're purposefully separate. Settings reference volumes and scripts, and contain the various options. They can also reference shell scripts.

Scheduled copies are copied to their own location and those settings are separate.

So, settings and scheduled copies store the same things (source, destination, script, options) with scheduled copies additionally storing the scheduling information? But the stuff stored in scheduled copies cannot be accessed manually (eg, if you want another scheduled copy of the same source, script and options but another destination), to get quick access to these, you have store them also as settings?

When we had an installer, the "standard scripts" folder was read-only so you couldn't change them. But, you can include your own scripts, too - ours are on the "same level" as yours in the "rights" sense. The idea, though, is to use the tool properly - and I do document that in the User's Guide.

Yes, many improvements could be made in the scripting area...and many others. The question is taking the engineering time available and applying it to areas that benefit the most users, which doesn't necessarily mean the parts of the design that are objectively the "worst" (but not necessarily used much).

Yes, dealing with the recovery partition seems a more urgent task (eg, when putting a new HDD into a computer, you cannot easily use SD to clone things from the old HDD as it worked fine in the pre-recovery partition.