The `read` builtin accepts backslash notation for common non-printing
characters by default, like `\t` and `\n`. This requires that any
literal backslashes must also be escaped as `\\`.

Given that `gpg -e` does not interpret input, the `read` invocations are
changed to do the same.

Also, the right hand side of an `==` comparison within `[[ ]]` must be
quoted in order to suppress pattern metacharacter expansion. Quoting the
bash manual:

    When the == and != operators are used, the string to the right of
    the operator is considered a pattern and matched according to the
    rules described below under Pattern Matching.

- relicensed to GPLv2+
- added -f command-line flag
- added -d DEFAULT_GROUP flag

Reported-by: Paul Wise <pabs@debian.org>

Redefine GNUPG and GETOPT for port paths
Redefine tmpdir() for a different ramdisk path

- Only use secret keys
- Use entire UID
- --with-colons makes parsing easy

Names and email addresses (if present) are included

only auto-expand if there is a single completion match

Common git commands, --reencrypt, --force.