Re: Line 28: Don't know subversion well enough to make a firm suggestion maybe one of these would work:

a. Have vcs_remove_svn always use --force. (seems unsafe)
b. Add a vcs_unregister function that is like vcs_remove but vcs_unregister_subversion adds --force
c. Have vcs_remove_svn run the code as normal but if there is an error, try again with --force. (seems odd to do it that way)

using --force in an automated tool is generally not a good idea. aside from being slightly dangerous, you can end up creating a tree conflict which can be a pain to resolve.

I think the best approach would be to somehow catch the error and notify the user on how to handle this manually.

I'm terrible in bash, so I'll use Python to describe:

Right now this is the behavior:

remove_filename_from_cryptlist
vcs_remove "$encrypted_file"
# basically, we exit above on the failure
exit 1
vcs_notice "$unencrypted_file"

and I'd like to try and handle it like this:

try:
    remove_filename_from_cryptlist
    vcs_remove "$encrypted_file"
    vcs_notice "$unencrypted_file"
except vcs_remove_error:
    echo "there is a conflict. you must manually deregister as follows:"
    echo "instructions"
    exit 

is there any way in bash to catch an error like that?