From 3d6340e8c59ee11a95e03fb213ad9b228be47833 Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Fri, 16 Sep 2016 15:06:26 +0200 Subject: core: Map GPGME_STATUS_EOF to the empty string. * src/status-table.c (_gpgme_status_to_string): Return "" for EOF. * src/engine-gpg.c (read_status): Ditto. The old code accidently used GPGME_STATUS_EOF which is the integer 0 and neiteyr NULL nor a string. Signed-off-by: Werner Koch --- doc/gpgme.texi | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/gpgme.texi b/doc/gpgme.texi index dc5a1407..18fb6d5c 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -4464,12 +4464,13 @@ could not be started. @tindex gpgme_interact_cb_t The @code{gpgme_interact_cb_t} type is the type of functions which @acronym{GPGME} calls if it a key interact operation is on-going. The -status keyword @var{status} and the argument line @var{args} are passed -through by @acronym{GPGME} from the crypto engine. The file -descriptor @var{fd} is -1 for normal status messages. If @var{status} -indicates a command rather than a status message, the response to the -command should be written to @var{fd}. The @var{handle} is provided -by the user at start of operation. +status keyword @var{status} and the argument line @var{args} are +passed through by @acronym{GPGME} from the crypto engine. An empty +string represents EOF. The file descriptor @var{fd} is -1 for normal +status messages. If @var{status} indicates a command rather than a +status message, the response to the command should be written to +@var{fd}. The @var{handle} is provided by the user at start of +operation. The function should return @code{GPG_ERR_FALSE} if it did not handle the status code, @code{0} for success, or any other error value. -- cgit v1.2.3