Run/Debug Configuration: Dart Command Line App
In this dialog box, create a configuration for running and debugging Dart code executed by Dart VM.
On this page:
Dart Command Line Application-specific configuration settings
Item | Description |
---|---|
Name | In this text box, specify the name of the run/debug configuration. |
Share | Select this check box to make the run/debug configuration available to other team members. The shared run/debug configurations are kept in separate xml files under This check box is not available when editing the run/debug configuration defaults. |
Dart file | In this text box, specify the Dart file to start the application from. The file must contain a main() method. |
VM options | In this text box, specify the options to launch the Dart Virtual Machine with. |
Program arguments | In this field, optionally type the arguments to start the application with. |
Working Directory | By default, the field is empty and the Dart package root is used as the working directory. |
Environment Variables | In this field, optionally specify the environment variables for your Dart application. Click to open the Environment Variables dialog box, where you can create variables and specify their values. You can also copy and paste the contents of the field without opening the Environment Variables dialog box. |
Toolbar
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Click this button to add a new configuration to the list. | |
Alt+Delete | Click this button to remove the selected configuration from the list. | |
Ctrl+D | Click this button to create a copy of the selected configuration. | |
Edit defaults | Click this button to edit the default configuration templates. The defaults are used for newly created configurations. | |
or | Alt+Up or Alt+Down | Use these buttons to move the selected configuration or folder up and down in the list. The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar. |
Move into new folder / Create new folder | Use this button to create a new folder. If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created. Move run/debug configurations to a folder using drag-and-drop, or the buttons. | |
Sort configurations | Click this button to sort configurations in alphabetical order. |
Common options
Item | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations. | ||||||||||||||||||||||||
Defaults | This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations. | ||||||||||||||||||||||||
Share | Select this check box to make the run/debug configuration available to other team members. The shared run/debug configurations are kept in separate xml files under This check box is not available when editing the run/debug configuration defaults. | ||||||||||||||||||||||||
Single instance only | If this check box is selected, this run/debug configuration cannot be launched more than once. Every time a new run/debug configuration is launched, RubyMine checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources. If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window. | ||||||||||||||||||||||||
Before launch | Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list.
|