From d3bd8fff863f62b6d0e228aea754efbbde861e9a Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Thu, 10 Apr 2014 14:17:19 +0200 Subject: Actually implement flags for gpgme_op_spawn. * src/spawn.c (gpgme_op_spawn_start, gpgme_op_spawn): Pass FLAGS dow to spawn_start and add FLAGS args along the call path. * src/engine-spawn.c (engspawn_start): Hack to automagically provide argv[0]. --- 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 027e1eff..7697ff12 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -5261,12 +5261,13 @@ with the GPGME API. The function @code{gpgme_op_spawn} runs the program @var{file} with the arguments taken from the NULL terminated array @var{argv}. If no -arguments are required @var{argv} may be given as @code{NULL} (in that -case GPGME uses the basename of @var{file} for @code{argv[0]}). The -file descriptors @code{stdin}, @code{stdout}, and @code{stderr} are -connected to the data objects @var{datain}, @var{dataout}, and -@var{dataerr}. If NULL is passed for one of these data objects the -corresponding file descriptor is connected to @file{/dev/null}. +arguments are required @var{argv} may be given as @code{NULL}. In the +latter case or if @code{argv[0]} is the empty string, GPGME uses the +basename of @var{file} for @code{argv[0]}. The file descriptors +@code{stdin}, @code{stdout}, and @code{stderr} are connected to the +data objects @var{datain}, @var{dataout}, and @var{dataerr}. If NULL +is passed for one of these data objects the corresponding file +descriptor is connected to @file{/dev/null}. The value in @var{flags} is a bitwise-or combination of one or multiple of the following bit values: -- cgit v1.2.3