Add command --locate-key.

Fix auto-key-locate processing of "nodefault".

1 files changed, 18 insertions, 0 deletions

diff --git a/doc/gpg.texi b/doc/gpg.texi
index ed8661302..267870267 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -291,6 +291,10 @@ secret key is not usable (for example, if it was created via
 @item --list-sigs
 @opindex list-sigs
 Same as @option{--list-keys}, but the signatures are listed too.
+@ifclear gpgone
+This command has the same effect as 
+using @option{--list-keys} with @option{--with-sig-list}.
+@end ifclear
 
 For each signature listed, there are several flags in between the "sig"
 tag and keyid. These flags give additional information about each
@@ -308,6 +312,10 @@ command "tsign").
 @item --check-sigs
 @opindex check-sigs
 Same as @option{--list-sigs}, but the signatures are verified.
+@ifclear gpgone
+This command has the same effect as 
+using @option{--list-keys} with @option{--with-sig-check}.
+@end ifclear
 
 The status of the verification is indicated by a flag directly following
 the "sig" tag (and thus before the flags described above for
@@ -316,6 +324,16 @@ successfully verified, a "-" denotes a bad signature and a "%" is used
 if an error occured while checking the signature (e.g. a non supported
 algorithm).
 
+@ifclear gpgone
+@item --locate-keys
+@opindex locate-keys
+Locate the keys given as arguments.  This command basically uses the
+same algorithm as used when locating keys for encryption or signing and
+may thus be used to see what keys @command{@gpgname} might use.  In
+particular external methods as defined by @option{--auto-key-locate} may
+be used to locate a key.  Only public keys are listed.
+@end ifclear
+
 
 @item --fingerprint
 @opindex fingerprint