Scopes and file colors
A scope 
is a group of files and folders in a project. You can use scopes to visually distinguish project items in different IDE views and to limit the range of specific operations.
Scopes are designed to logically organize files in your project: test sources can go to the test-related scope, and production code can be associated with the scope of production files. These logical chunks make your project easier to manage. For example, running test-related inspections only in test classes takes less time than if you run them in all files in your application.
CLion comes with a set of predefined scopes, but you can also create custom scopes. There, you can include any files and folders. For example, a custom scope can include only those files in the project for which you are responsible.
In CLion, scopes are used in code inspections, some refactorings, search, in copyright settings, in various features for code analysis, and so on.
There are 2 types of scopes: local and shared.
Local scopes are stored in the IDE configuration directory, that is why they are not shared through VCS and are not available to other members of your team.
Using shared scopes makes sense if your project is under version control. If you don't use a VCS, local scopes will be sufficient to cover your needs.
Define a new scope
In CLion, there's a set of predefined scopes, but you can also define your own scopes.
Press Ctrl+Alt+S to open settings and then select .
Click the Add Scope button (
) and select what kind of scope you want to define: local or shared.You can change the state of the selected scope (local or shared) later using the Share through VCS checkbox.
In the dialog that opens, name the new scope and click OK.
Add files to the new scope. Select the necessary items in the project tree and click one of the options located on the right from the tree:
Include: include the selected items. If you are including a folder, this action adds only the files located inside this folder. All nested subfolders and their contents will not be included.
Include Recursively: include the selected folder together with the nested subfolders and their contents.
Exclude: exclude the selected items from the scope. If you are excluding a folder, this action removes only the files located inside this folder. All nested subfolders and their contents will remain in the scope.
Exclude Recursively: exclude the selected folder together with the nested subfolders and their contents.
As you add files to the scope, CLion creates an expression and displays it in the Pattern field.
Instead of using the buttons, you can also type a pattern in the Pattern field manually using the scope language syntax reference.
Apply the changes and close the dialog.
Files and folders displayed for the selected scope are shown in different colors to help you understand what is included and what is not:
Files and folders included in the scope.
Folders that contain both excluded and included files and folders.
Files and folders that are excluded from the selected scope.
After you create a custom scope, you can find it in the Project tool window and in all dialogs that allow you to limit the number of files to which you want to apply an action.
Predefined scopes
CLion provides a set of predefined scopes. The IDE adds files to these scopes automatically based on the information about them. Note that these scopes cannot be modified.
List of predefined scopes
Project Files: includes all files within the project root directory. For more information, refer to Project root directory.
All Changed Files: includes all the recently changed files.
Scratches and Consoles: includes all files from the Scratches and Consoles directory located in the Project tool window .
Recently Viewed Files and Recently Changed Files: includes the last 50 files that you have opened or modified in the editor. You can change the number of recent files in the Limits area on the page of the Settings dialog (Ctrl+Alt+S) .
Project and Libraries: includes all files within the project content roots and also all module dependencies (libraries and SDKs).
Project Files Tracked by Git: includes all files within the project content roots that are under version control in Git.
Project Files Excluding Git-Ignored: includes all files within the project content roots, both under version control in Git and unversioned, excluding the files specified in
.gitignore.Open Files: includes the files that are currently open in the editor.
Local Changes (These scopes appear if VCS integration is enabled)
All Changed Files: includes the modified files with changes that are not yet added to VCS from all changelists.
Default Changelist: includes the modified files with changes that are not yet added to VCS from the Default changelist.
'Changelist name': includes the modified files with changes that are not yet added to VCS from a specific custom changelist.
Data Sources
Context Data Sources: includes the data source you are working with at the moment. The context can be defined either from the console you are working with, the data editor, or by selecting it in the database explorer.
Connected Data Sources: includes the data sources that have an active connection.
All Data Sources: includes all added data sources.
Associate scopes with colors
Files that belong to different scopes can be highlighted in different colors in search results, in editor tabs, and in the Project tool window Alt+1.
To each scope, you can assign its own color. For example, you can assign a color to the Open Files scope and configure the IDE to show this color in the Project tool window . In this case, the files that you are currently working with in the editor will be colored in the project tree. This makes project navigation faster and simpler. Note that file colors work only in association with scopes.
Similarly to scopes, color associations can be local and shared.
Local colors are only visible to you and are not shared through VCS.
Create a new color association
Press Ctrl+Alt+S to open settings and then select .
Make sure that the Enable file colors checkbox is selected, and then choose where you want to use the colors: select Use in editor tabs or Use in project view.
If you select the Use in project view checkbox, you will see colors in the Project tool window Alt+1 and in search results (for example, in the Find in Files dialog Ctrl+Shift+F).
Click the Add button (
) and select the scope for which you want to configure a color.You can select one of the pre-defined scopes or use a custom scope.
Click the arrow
next to the necessary scope and select a color from the list that opens.To configure your own color, click Custom.
To edit a color, click the cell that corresponds to the necessary scope in the Color column and select a new color from the list.
To share a color through a VCS, select the checkbox on the corresponding line in the Share through VCS column. If the checkbox is cleared, the color will be used locally.
Apply the changes and close the dialog.
If a file is included in several scopes, the order of the scopes becomes important: CLion processes the scopes from the top to the bottom starting from local scopes. It means that the IDE will apply the color of the last scope in the list to such a file.
You can change the order of the scopes if you want CLion to process color associations in a different order.
Change the order of scopes
Press Ctrl+Alt+S to open settings and then select .
Select the scope that you want to move and click the Move Up (
) or Move Down (
) button. Alternatively, press Alt+Up or Alt+Down.Apply the changes and close the dialog.