Use this page to create, manage, and edit live templates.
On this page:
- List of available live templates
- Context menu of a live template
- Template editing area
- Side note about predefined template variables
- Predefined functions to be used in live template variables
List of available live templates
|Item||Tooltip and shortcut||Description|
|By default expand with||Use this drop-down list to specify the default invocation key for all templates. Individual expansion keys for the particular templates are defined in the editing area. |
When Custom is selected, the Change link appears next to the drop-down, leading you to the Keymap page.
|Live Templates||This list shows all currently available template abbreviations supplied with their descriptions. The abbreviations are grouped below nodes and sorted alphabetically within each group. To activate a template or an entire group, select the check box to its left.|
|Click this button to have a new template item added to the current group of template. You can define the template abbreviation, description, text, variables, expansion key, and context in the editing area below.|
|Click this button to have the selected live template removed from the list.|
|Duplicate||Click this button to create a new template based on the selected template. A new template item is added to the current node and the fields in the Template Text area show the definition of the selected template.|
|Restore||Click this button to restore the deleted live templates. This button is only enabled when the changes are applied.|
Context menu of a live template
|Move||Choose a group to move the selected template to.|
|Change context||Choose this command to modify the set of contexts where the current template is enabled. Upon choosing this command, a list of supported language contexts is displayed. To make CLion consider a context sensitive to the template, select a check box next to the context name. |
The available context types depend on the enabled plugins.
|Copy||Choose this command to create a serialized template XML in the system clipboard. Refer to section Sharing Live Templates.|
|Paste||Choose this command to paste an XML representation of the copied templates to the selected group of templates. Refer to section Sharing Live Templates.|
|Restore defaults||This command only appears on the context menus of the modified templates, marked blue. Choose this command to restore the default template settings.|
Template editing area
The focus is moved to this area in the following cases:
- When you click the Add or Copy button.
- When you select a live template in the list.
- When you select a fragment of code in the editor and choose Tools | Save as Live Template.
Use controls of this area to create new live templates and edit the settings for the existing ones.
You can navigate through the Template Text Area using the hot keys that are marked in the field labels.
|Abbreviation||In this text box, specify the template abbreviation.|
|Description||In this text box, provide optional description of a template or an example of its usage.|
|Template Text||In this text box, type the template body that may contain plain text and variables in the format |
When editing the live template variables, mind the following helpful hints:
Side note about predefined template variables
You cannot edit the predefined live template variables
|Applicable in:||This read-only field shows the languages and/or pieces of code where the editor should be sensitive to the template. Upon pressing Ctrl+J in such context, CLion displays a list of templates that are valid for this context.|
|Change|| Click this link to modify the set of contexts where the current template is enabled. Upon clicking the link, a list of supported language contexts is displayed. To make CLion consider a context sensitive to the template, select a check box next to the context name. |
The available context types depend on the enabled plugins.
|Edit Variables||Click this button to open the Edit Template Variables dialog box, where you can define how CLion should process template variables upon template expansion. Edit Template Variables dialog box contains a complete list of available functions. See the list of predefined functions below on this page.|
|Options||In this area, define the behavior of the editor when a template is expanded. |
Predefined functions to be used in live template variables
|Returns the string passed as a parameter, converted to camel case. For example, |
|Capitalizes the first letter of the name passed as a parameter.|
|Capitalizes the all letters of a CamelCase name passed as a parameter, and inserts an underscore between the parts. For example, if the string passed as a parameter is |
|This expression substitutes for the class name completion at the variable position.|
|Returns the contents of the system clipboard.|
|Returns CamelCase string out of snake_case string. For example, if the string passed as a parameter is |
|This expression substitutes for the code completion invocation at the variable position.|
|This expression substitutes for the smart type completion invocation at the variable position.|
| Returns the current system date in the specified format. |
By default, the current date is returned in the default system format. However, if you specify date format in double quotes, the date will be presented in this format:
|Replaces the first letter of the name passed as a parameter with the corresponding lowercase letter.|
|List of comma-delimited strings suggested for completion at the template invocation.|
|Escapes the specified string.|
|Returns file name with extension.|
|Returns file name without extension.|
|Returns the first word of the string passed as a parameter.|
|Returns the current line number.|
|Returns lower case separated by dashes, of the string passed as a parameter. For example, the string |
|Returns a list of visible objects that contain the member functions, listed as parameters.|
|Declares the left-side variable with a type of the right-side expression. It is used in the iterations group to have a single template for generating both raw-type and Generics Collections.|
|Returns snake_case string out of CamelCase string passed as a parameter.|
|Returns string separated with spaces out of CamelCase string passed as a parameter. For example, if the string passed as a parameter is |
|Suggests the name of an index variable. Returns |
|Suggests the name for a variable based on the variable type and its initializer expression, according to your code style settings that refer to the variable naming rules.|
For example, if it is a variable that holds an element within iteration, CLion makes a guess on the most reasonable names, also taking into account the name of the container being iterated.
|Doesn't suggest |
|Returns the current system time.|
|Returns the string passed as a parameter with CamelHump letters substituting for underscores. For example, if the string passed as a parameter is |
|Returns the string passed as a parameter with spaces substituting for underscores.|
|Returns the name of the current user.|
|Returns a variable that is an instance of object used as a range-expression in a loop.|
|Returns a variables that is an instance of object that contain |