manpage claims: ".. --passphrase string Use string as the passphrase. .."
Gpg straightforwardly worked like this in previous versions.
Probably since gpg2, the supplied passphrase is ignored and an
annoying "pinentry" popup pops up.
I can remedy if I provide "--batch" and (!) "--pinentry-mode loopback"
While this is sort of documented to those who do not get lost in the
docs, see quotation below, how many options does gpg want to read in
order to respect "--passphrase"?
Will you fix?
Microsoft Windows [Version 10.0.17134.165]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.
gpg (GnuPG) 2.2.9-unknown
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Use STRING as the passphrase. This can only be used if only one passphrase is supplied. Obviously, this is of very questionable security on a multi-user system. Don't use this option if you can avoid it. Note that since Version 2.0 this passphrase is only used if the option '--batch' has also been given. Since Version 2.1 the '--pinentry-mode' also needs to be set to 'loopback'.