Prior to https://dev.gnupg.org/rG584b65ad7e937710a4fc6db42d6849bb3449d6ef, running gpg --decrypt --list-only --verbose --logger-fd 1 test.asc with log-file set in gpg.conf would produce output like:

gpg: public key is 0xA1F9838CBD46A1A8
gpg: using subkey 0xA1F9838CBD46A1A8 instead of primary key 0xDFE691AE331BA3DB
gpg: encrypted with 4096-bit RSA key, ID 0xA1F9838CBD46A1A8, created 2011-12-05
      "James McCoy (Debian) <jamessan@debian.org>"

After that commit, there is no output at all because it all gets redirected to the log file.

This breaks users of the vim-gnupg plugin that have log-file set in their config, since I now cannot determine whether a file was encrypted symmetrically or asymmetrically.

Typically, command-line options override ones from the config file, but these are treated as separate options so log-file wins out.

I'm also open to suggestions of better ways to handle this that are backward compatible with older gpg versions, if there's a more stable way to handle this (like --fixed-list-mode for querying keys).