From: Kevin Locke Date: Thu, 18 Feb 2016 21:26:26 +0000 (-0800) Subject: doc: clarify child_process.execFile{,Sync} file arg X-Git-Tag: v4.4.0~43 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1ea49bb399194b70423a0e573bf5a75dad191ad5;p=platform%2Fupstream%2Fnodejs.git doc: clarify child_process.execFile{,Sync} file arg The changes to the file argument of execFile in #4504 make it appear that execFile requires an absolute or relative path to the executable file, when it also supports a filename which will be resolved using $PATH. Although the example makes this clear, assuming there isn't a node binary in $CWD, it's easy to overlook. This commit clarifies that point. It also updates the argument description for execFileSync to match, since it was overlooked in #4504 and behaves identically. PR-URL: https://github.com/nodejs/node/pull/5310 Reviewed-By: James M Snell --- diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index 107145e..9ab3b2d 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -183,7 +183,7 @@ replace the existing process and uses a shell to execute the command.* ### child_process.execFile(file[, args][, options][, callback]) -* `file` {String} A path to an executable file +* `file` {String} The name or path of the executable file to run * `args` {Array} List of string arguments * `options` {Object} * `cwd` {String} Current working directory of the child process @@ -497,7 +497,7 @@ configuration at startup. ### child_process.execFileSync(file[, args][, options]) -* `file` {String} The filename of the program to run +* `file` {String} The name or path of the executable file to run * `args` {Array} List of string arguments * `options` {Object} * `cwd` {String} Current working directory of the child process