sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #14466
[Bug 1076372] Re: [request] improvement for run command
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.
** Changed in: sikuli
Status: New => In Progress
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => x1.0
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1076372
Title:
[request] improvement for run command
Status in Sikuli:
In Progress
Bug description:
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()
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1076372/+subscriptions
References