Troubleshooting Command Launching & Output

Clicking on the Run Button does not launch a Command:
A Command will not launch if there is no Working Directory specified. We will fix this soon, so that the Run button is not enabled in this case. The workaround for this is just to pick a directory either by Browsing from within the Command View, or by picking a directory in the Navigator View.

Pressing <Enter> does not launch a Command:
There is known problem in the Command View with <Enter> not causing the command to start. We are looking into it. As a workaround, you can click the Run button or if you must use the keyboard...press <Tab> until the Run button is selected, then pressing the <Spacebar> will cause the Command to be run.

Trouble cancelling a command or commands that never finish:
Each command is launched on a background thread, so it is possible that a Cancel request will not be immediately received by a command thread. In some cases, commands may take a several seconds to actually get Canceled. You can tell if a Command is successfully cancelled by checking the Output View for the line "Command Cancelled by User Request"
We have also found some command combinations that can result in a command that never finishes and can cause the Desktop to slow down. One such command type is the following:

      ls | xargs grep "some text"

In some extreme cases it may be necessary to kill the "java.exe" process that the Studio Workbench is running in (via Task Manager). This will be fixed shortly.