Command-line interface
Use CLion features from the command line: open files and projects, view diffs, merge files, apply code style formatting, and inspect the source code.
tip
For information about running command-line tools from inside CLion, see Terminal.
Launcher for a standalone instance
The installation directory contains batch scripts and executables for launching CLion, formatting the source code, and running inspections. To use them from the Command Prompt cmd.exe, add the location of the CLion bin folder to the PATH environment variable. For example, if you installed CLion to C:
>set PATH=%PATH%;C:\Program Files\JetBrains\CLion\bin
This command changes the PATH environment variable for the current shell only (the current instance of cmd.exe). If you want to update it permanently for the current user, run setx:
>setx PATH "%PATH%;C:\Program Files\JetBrains\CLion\bin"
To update it system-wide for all users, run setx /M instead of setx.
tip
The installer can do this for you if you select Add launchers dir to the PATH on the Installation Options step of the setup wizard.
After you configure the PATH variable, you can run the executable from any working directory in the Command Prompt: clion64.exe. Alternatively, you can use the batch script: clion.bat.
Shell scripts generated by the Toolbox App
If you are using the Toolbox App to install and manage JetBrains products, it can create shell scripts for launching your IDEs from the command line.
Generate shell scripts
Open the Toolbox App and click
in the top right corner.In the Toolbox App Settings, enable Generate shell scripts.
If necessary, change the shell scripts location.
If you have several versions of the same IDE, the Toolbox App generates a shell script for each version with a unique name. You can change the name of the shell script for an IDE instance in the settings for this specific instance.
Change the name of the shell script
Open the Toolbox App.
Click
next to the relevant IDE instance and select Settings.At the bottom, change the Shell script name field.
By default, the Toolbox App puts shell scripts in a directory from the system PATH environment variable, so you can run the name of the script as a command to launch CLion from any working directory.
Command-line arguments
The launcher script accepts commands, options, and other arguments to modify its behavior:
Argument | Description |
|---|---|
No argument | Launch CLion. |
Path to file or directory | Open the file or directory specified as the argument. For more information, see Open files from the command line. |
Commands | |
| Open the diff viewer to see differences between two specified files. For more information, see Compare files from the command line. |
| Open the Merge dialog to merge the specified files. For more information, see Merge files from the command line. |
| Apply code style formatting to the specified files. For more information, see Format files from the command line. |
| Perform code inspection on the specified project. For more information, see Run code inspections from the command line. |
Options | |
| Do not show the splash screen when loading CLion. |
| Do not reopen projects and show the welcome screen. This can help if a project that was open crashes CLion for some reason. |
| Do not load manually installed plugins. This can help if a plugin that you installed crashes CLion for some reason. You will be able to start the IDE and either disable or uninstall the problematic plugin. |
| Wait for the files to be closed before returning to the command prompt. For example, you can open file.txt with the following command: The shell will be waiting until file.txt is closed. |