Merge pull request #15917 from brainsick/doc-os-commands
clarify OS.execute usage
This commit is contained in:
commit
d8390105c3
1 changed files with 12 additions and 1 deletions
|
@ -87,7 +87,18 @@
|
|||
<argument index="3" name="output" type="Array" default="[ ]">
|
||||
</argument>
|
||||
<description>
|
||||
Execute the binary file in given path, optionally blocking until it returns. A process ID is returned.
|
||||
Execute the file at the given path, optionally blocking until it returns.
|
||||
Platform path resolution will take place. The resolved file must exist and be executable.
|
||||
Returns a process id.
|
||||
For example:
|
||||
[codeblock]
|
||||
var output = []
|
||||
var pid = OS.execute('ls', [], true, output)
|
||||
[/codeblock]
|
||||
If you wish to access a shell built-in or perform a composite command, a platform specific shell can be invoked. For example:
|
||||
[codeblock]
|
||||
var pid = OS.execute('CMD.exe', ['/C', 'cd %TEMP% && dir'], true, output)
|
||||
[/codeblock]
|
||||
</description>
|
||||
</method>
|
||||
<method name="find_scancode_from_string" qualifiers="const">
|
||||
|
|
Loading…
Reference in a new issue