Run/Debug Configuration: XSLT
This run/debug configuration becomes available, when XPath View+XSLT Support plugin is enabled.
On this page
Getting access to the Run/Debug Configuration: XSLT dialog
Make sure the XPath View+XSLT Support plugin is enabled.
The plugin is bundled with PhpStorm and activated by default.
If the plugin is not activated, enable it on the Plugins page of the Settings / Preferences Dialog as described in Enabling and Disabling Plugins.
Settings tab
Advanced tab
In this tab, configure additional options that are not commonly required in run configurations.
Item | Description |
---|
Smart Error Handling |
- Clear this check box to have the console display full error messages including their complete stack traces,
when an error occurs during execution.
-
Select this check box to suppress showing staktraces
and have the console display only the relevant information about errors.
|
VM Arguments | In this text box, specify optional VM arguments to be passed to the VM where the XSLT script is executed.
These can be heap size, garbage collection options, file encoding, etc.
If the line of VM arguments is too long, click the button
and and type the text in the VM Arguments dialog box, that opens.
|
Working Directory | In this text box, specify the working directory to use. Type the path manually or
click the Browse button
and select the desired folder in the Working Directory dialog box, that opens.
If no folder is specified in text box, the working directory will be the one where the XSLT script file is located.
|
Toolbar
Common options
Item | Description |
---|
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.
|
Temporary configurations limit | Specify here the maximum number of temporary configurations to be stored and shown in the
Select Run/Debug Configuration drop-down list. |
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 .idea\runConfigurations folder,
while the local run/debug configurations are kept in
the .idea\workspace.xml .
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, PhpStorm 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.
Item | Keyboard shortcut | Description |
---|
|
Alt+Insert
| Click this icon to add a task to the list. Select the task to be added:
-
Run External tool.
Select this option to run an application which is external to PhpStorm.
In the dialog that opens, select the application or applications that should be run.
If the necessary application is not defined in PhpStorm yet, add its definition.
For more information, see Configuring Third-Party Tools and External Tools.
-
Run Another Configuration.
Select this option to have another run/debug configuration executed.
In the dialog that opens, select the configuration to run.
This option is available only if you have already at least one run/debug configuration in the current project.
-
Run File Watchers.
Select this option to have PhpStorm apply all the currently active file watchers,
see Using File Watchers for details.
-
Run Grunt task. Select this option to run a Grunt task.
In the Grunt task dialog box that opens, specify the
Gruntfile.js where the required task is defined,
select the task to execute,
and specify the arguments to pass to the Grunt tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.
- Run Gulp task. Select this option to run a Grunt task.
In the Gulp task dialog box that opens, specify the
Gulpfile.js where the required task is defined,
select the task to execute,
and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
-
Run npm Script. Select this check box to execute an npm script.
In the NPM Script dialog box that opens, specify the
package.json file where the required script is defined,
select the script to execute, choose the command to apply to it, and specify the arguments to execute the script with.
Specify the location of the Node.js interpreter and the parameters to pass to it.
- Compile TypeScript. Select this option to run the built-in TypeScript compiler
and thus make sure that
all the changes you made to your TypeScript code are reflected in the generated JavaScript files.
In the TypeScript Compile Settings dialog that opens, select or clear the Check errors check box
to configure the behaviour of the compiler in case any errors are detected:
-
If the Check errors check box is selected, the compiler will show all the errors
and the run configuration will not start.
-
If the Check errors check box is cleared, the compiler will show all the detected errors
but the run configuration still will be launched.
-
Generate CoffeeScript Source Maps.
Select this option to have the source maps for your CoffeeScript sources generated.
In the dialog that opens, specify where your CoffeeScript source files are located.
For more information, see CoffeeScript Support.
-
Run Phing target: Add this task to execute the specified Phing target
prior to running or debugging.
To appoint a Phing target, click the Browse button and select
the desired target in the Choose Phing Target to Execute dialog box, that opens.
-
Run Remote External tool: Add a remote SSH external tool. Refer to the section Remote SSH External Tools for details.
-
Upload files to Remote Host.
Select this option to have the application files automatically uploaded to the server according to the default server access configuration.
For more information, see Configuring Synchronization with a Web Server and Uploading and Downloading Files.
|
|
Alt+Delete
| Click this icon to remove the selected task from the list. |
|
Enter
| Click this icon to edit the selected task.
Make the necessary changes in the dialog that opens. |
|
Alt+Up
|
Click this icon to move the selected task one line up in the list. |
|
Alt+Down
|
Click this icon to move the selected task one line down in the list. | Show this page | |
Select this check box to have the run/debug configuration settings shown prior to
actually starting the run/debug configuration. | Active tool window | | Select this option if you want the Run/Debug tool windows
to be activated automatically when you run/debug your application. This option is enabled by default. |
|
Last modified: 24 November 2016