gpg has an annoying "feature": it avoids to overwrite files. If in interactive mode, "gpg2 -o foo" will ask the user whether to override foo or not, otherwise will just refuse to work. not nice. working around this by making gpg2 write to stdout, and redirecting stdout to that file. Then restore stdout for sanity :) While here, also make `writepass' fail if gpg fails.

'gen' now is happy to override files. since we're using a version control system anyway, there's no point in being picky about changing files. If one overrides a password by mistake, the old one is still available thanks to got.

gen now has a -n option for no-op that avoids persisting the password and now prints the generated password by default. This comes in handy in various cases, for example now it's possible to: $ plass gen foobar | clip A foobar2.gpg Created commit c1d55a274bd28103271a7e4d0c4f83266fc14926 Like the 'tee' subcommand, add -q to suppress printing the password if desired.