threads / patch / 20487

patchapi-run-command.txt: describe error behavior of run_command functions

Subject: [PATCH js/run-command-updates] api-run-command.txt: describe error behavior of run_command functions

## tl;dr

2 messages between Aug 8, 2009 and Aug 8, 2009. Diffs are folded; open one to read it.

replies: 1people: 2as markdown or json

Johannes Sixt· Aug 8, 2009, 20:44 UTC · lore
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
---
 Documentation/technical/api-run-command.txt |   31 ++++++++++++++++++++++++--
 1 files changed, 28 insertions(+), 3 deletions(-)
Show changes to Documentation/technical/api-run-command.txt +28 −3
diff --git a/Documentation/technical/api-run-command.txt 
b/Documentation/technical/api-run-command.txt
index 2efe7a4..b26c281 100644
--- a/Documentation/technical/api-run-command.txt
+++ b/Documentation/technical/api-run-command.txt
@@ -35,12 +35,32 @@ Functions
 	Convenience functions that encapsulate a sequence of
 	start_command() followed by finish_command(). The argument argv
 	specifies the program and its arguments. The argument opt is zero
-	or more of the flags `RUN_COMMAND_NO_STDIN`, `RUN_GIT_CMD`, or
-	`RUN_COMMAND_STDOUT_TO_STDERR` that correspond to the members
-	.no_stdin, .git_cmd, .stdout_to_stderr of `struct child_process`.
+	or more of the flags `RUN_COMMAND_NO_STDIN`, `RUN_GIT_CMD`,
+	`RUN_COMMAND_STDOUT_TO_STDERR`, or `RUN_SILENT_EXEC_FAILURE`
+	that correspond to the members .no_stdin, .git_cmd,
+	.stdout_to_stderr, .silent_exec_failure of `struct child_process`.
 	The argument dir corresponds the member .dir. The argument env
 	corresponds to the member .env.
 
+The functions above do the following:
+
+. If a system call failed, errno is set and -1 is returned. A diagnostic
+  is printed.
+
+. If the program was not found, then -1 is returned and errno is set to
+  ENOENT; a diagnostic is printed only if .silent_exec_failure is 0.
+
+. Otherwise, the program is run. If it terminates regularly, its exit
+  code is returned. No diagnistic is printed, even if the exit code is
+  non-zero.
+
+. If the program terminated due to a signal, then the return value is the
+  signal number - 128, ie. it is negative and so indicates an unusual
+  condition; a diagnostic is printed. This return value can be passed to
+  exit(2), which will report the same code to the parent process that a
+  POSIX shell's $? would report for a program that died from the signal.
+
+
 `start_async`::
 
 	Run a function asynchronously. Takes a pointer to a `struct
@@ -143,6 +163,11 @@ string pointers (NULL terminated) in .env:
 To specify a new initial working directory for the sub-process,
 specify it in the .dir member.
 
+If the program cannot be found, the functions return -1 and set
+errno to ENOENT. Normally, an error message is printed, but if
+.silent_exec_failure is set to 1, no message is printed for this
+special error condition.
+
 
 * `struct async`
 
-- 
1.6.4.87.g9ec6e
Junio C Hamano· Aug 8, 2009, 20:53 UTC · re: Johannes Sixt · lore

Re: [PATCH js/run-command-updates] api-run-command.txt: describe error behavior of run_command functions

Johannes Sixt <j6t@kdbg.org> writes:
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---
>  Documentation/technical/api-run-command.txt |   31 ++++++++++++++++++++++++--
>  1 files changed, 28 insertions(+), 3 deletions(-)
Thanks.

← back to recent threads