From a3d1b15db26f5320f4b191f77a0904acc5220c4b Mon Sep 17 00:00:00 2001 From: Moritz Schulte Date: Tue, 23 Dec 2003 09:08:06 +0000 Subject: [PATCH] 2003-12-23 Moritz Schulte * gpgme.texi (Listing Keys): Minor clarification for gpgme_get_key. --- doc/ChangeLog | 5 +++++ doc/gpgme.texi | 3 ++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 0064e2d2..1589e416 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2003-12-23 Moritz Schulte + + * gpgme.texi (Listing Keys): Minor clarification for + gpgme_get_key. + 2003-10-06 Marcus Brinkmann * gpgme.texi (Signal Handling): New section. diff --git a/doc/gpgme.texi b/doc/gpgme.texi index 48094548..8c34f897 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -2477,7 +2477,8 @@ following function can be used to retrieve a single key. The function @code{gpgme_get_key} gets the key with the fingerprint (or key ID) @var{fpr} from the crypto backend and return it in @var{r_key}. If @var{secret} is true, get the secret key. The -currently active keylist mode is used to retrieve the key. +currently active keylist mode is used to retrieve the key. The key +will have one reference for the user. If the key is not found in the keyring, @code{gpgme_get_key} returns the error code @code{GPG_ERR_NO_ERROR} and *@var{r_key} will be set to