Path containing colon gives error

[thomasmitchell]

cp to a path with two colons yields:

!! cannot write to paths in /path:key notation

We should be able to handle paths with colons in them, and even if that weren't true, that's a bad error.

[thomasmitchell]

This comes down to that we have code for the purpose of safe set that errors out if the path segment has a colon in it. This means that you technically can't write to any path with a colon in it. Is this a restriction that should be removed?

[dennisjbell]

safe gen also has this issue:

$ safe gen secret/test/pw:test:me
!! cannot write to paths in /path:key notation