In this part:
Changing CLion properties
CLion makes it possible to change the
*.vmoptions and the
idea.properties files without editing them in the CLion installation folder.
To create an empty
idea.properties file or to copy the
*.vmoptions file, choose or from the main menu respectively.
Managing the *.vmoptions file
The location of the
*.vmoptions file depends on your operating system:
- For Windows:
<CLion installation folder>/bin/clion64.exe.vmoptions
- For *NIX:
<CLion installation folder>/bin/clion64.vmoptions
- For macOS, you need to make a copy of the
clion.vmoptionsfile in the IDE preferences folder and then edit this copy. The reason is that the app bundle is signed and you should not modify any files inside the bundle.
To avoid editing files in the CLion installation folder, do one of the following:
- From the main menu, choose
clion.vmoptionsfile in the user home directory. to create a copy of the
- Copy the existing file from the CLion installation folder somewhere and save the path to this location in the
- Copy the existing
<CLion installation folder>/bin/clion.exe.vmoptionsor the
<CLion installation folder>/bin/clion64.exe.vmoptionsfile from the CLion installation folder into your user home directory.
Then edit this file in the new location.
CL_VM_OPTIONS environment variable is defined, or the
*.vmoptions file exists, this file is used instead of the one located in the CLion installation folder.
Example: Increasing the heap size
To increase CLion heap size, you should copy the original
clion.vmoptions file to the above-mentioned location, and then modify the
Managing the idea.properties file
idea.properties file located in the
bin directory of the CLion installation folder should not be edited. Instead of editing the original
idea.properties file, create an
idea.properties file in the following location, open it for editing and add the required properties:
- For Windows:
- For *NIX:
- For macOS:
To open the
idea.properties file in the editor, choose . If the file does not exist yet, CLion creates it and opens in the editor.
Example: Changing the case of unicode literals
CLion allows defining whether non-ascii characters should use literals like
This behavior is controlled by the
idea.native2ascii.lowercase system property. By default, upper-case characters are used.
If you wish to use lower-case characters, create the
idea.properties file in the location specified above, open it for editing and add the following line:
Specifying custom JDK, properties, or vmoptions files across platforms
A custom JDK, as well as
*.vmoptions files are specified across platforms in a unified way.
All launchers look at the following environment variables: