semantics of gnupg --keyserver in 2.1

[Daniel Kahn Gillmor]

in GnuPG 2.1, keyserver operations are delegated to the dirmngr daemon.

This is a good move overall, because it means the daemon can do things
like keep track of which keyservers it has tried recently.

however, it means that some commands that users may be used to won't do
what they expect.  For example, in 2.1:

  gpg --keyserver foo.example --recv 0xdeadbeef

won't actually try to talk to foo.example, if dirmngr is already started
and has decided that it will use bar.example (e.g. from
~/.gnupg/gpg.conf).

Should gpg warn about the fact that --keyserver is being ignored here?

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: </pipermail/attachments/20141216/bd8efa6a/attachment.sig>