[request] improvement for run command

[RaiMan]

In GUI mode the run(command) should show the console window.

In CLI mode the run(command) could optionally show the console window.

Either way, it should check the exit code and either return it or fail.

Without such improvement, it's just like submodule.call()

[RaiMan (raimund-hocke)]

based on https://github.com/sikuli/sikuli/issues/21

actually the run() command is implemented using java.lang.Runtime.getRuntime().exec(command string) and it returns the command output as a list of lines.
This is comparable to an implementation on the Jython level using os.popen() (or subprocess.popen() better).

In both cases these commands are run in a separate process and do not have a console window at all (just sysin, sysout and syserr).

Nevertheless: I have it on my list to improve it. And to optionally show the command output in a window seems to be a good idea.

[eptgrant (ept-grant)]

Hello,

I've made an alternative Run() method recently and I thought i'd share it.

I initially needed a different method as Sikuli was hanging when I was executing remote commands (psexec, winrs etc), as the external program would fail, and send the result back through the error pipe (which the old method wasn't handling).

Feel free to use it as you like.

Grant.

[RaiMan (raimund-hocke)]

Thanks for contribution.

I already fixed this with version 1.0.1, since I needed it myself internally ;-)

The run() now handles parameters with enclosing apostrophes correctly, as well as the usage of \<space> and returns:

<stdout line1>
<stdout line2>
<stdout line3>
...
*** error ***
<stderr line1>
<stderr line1>
<stderr line1>
...
<stderr exception message>

the error part is only appended if the err pipe has some content or the command execution forces an exception.