In this section:
- Changing CLion properties
- Managing *.vmoptions file
- Managing idea.properties file
- Specifying custom JDK, properties or vmoptions files across platforms
Changing CLion properties
CLion makes it possible to change
idea.properties files without editing them in the CLion installation folder.
To create an empty
idea.properties file or to copy
*.vmoptions file, choose
on the main menu respectively. Refer to the
menu items description for details.
Managing *.vmoptions fileFor Mac OS X systems: The file
/Applications/clionXX.app/Contents/bin/clion.vmoptionsshould be copied to
To avoid editing files in the CLion installation folder, one should:
- Do one of the following:
- Copy the existing file from the CLion installation folder somewhere and save the
path to this location in the environment variable
- Copy the existing file
<CLion installation folder>/bin/clion$BITS.vmoptionsfrom the CLion installation folder into the location under user home:
- For *NIX:
- For Windows:
The value of the variable BITS depends in the JVM used to run CLion:
Refer to the support article Selecting the JDK version the IDE will run under for details.
- For *NIX:
- Copy the existing file from the CLion installation folder somewhere and save the path to this location in the environment variable
- Edit this file in the new location.
CL_VM_OPTIONS environment variable is defined, or the
*.vmoptions file exists,
then this file is used instead of the file 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 IDEA.properties file
idea.properties, located in the
directory of the CLion installation folder, should not be edited. Instead of editing the original
idea.properties, create file
in the location specified below, open it for editing and add the required
So, depending on your platform:
- For Windows: in
- For *NIX: in
- For Mac OS X: in
Example: Changing case of unicode literals
CLion allows defining whether non-ascii characters should use literals like
This behavior is controlled by the system property
idea.native2ascii.lowercase. By default,
upper case characters are used.
If it is desirable to use lower case characters, create the 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,
*.vmoptions files are specified across platforms in
a unified way.
All the launchers look at the following environment variables: