![]() Select or press Ctrl+Alt+Shift+H.IntelliJ IDEA checks the spelling of all your source code, including variable names, text in strings, comments, literals, and commit messages. You can also change the highlighting level from the main menu. Hover the mouse over the widget in top-right corner of the editor and select another level from the Highlight list:Īll Problems: (default) highlight syntax problems and problems found by inspections. Change the highlighting level for a fileīy default, CLion highlights all detected code problems. For more information, refer to Change inspection severity in all scopes. Find the necessary inspection in the list and change its severity as you like. If you want to restore the highlighting, press Ctrl+Alt+S to open the IDE settings and select Editor | Inspections. The name of the inspection for which you are changing the severity is written above the inspection's options. Ĭlick the right arrow next to the fix to open the inspection's options and select Disable highlighting, keep fix. ![]() Locate the inspection fix that is marked with. Place the caret at a code element highlighted by an inspection in the editor and press Alt+Enter.Ī list with available fixes and context actions opens. In this case, the inspection remains enabled and provides a fix, but the severity changes to No highlighting (fix available). You can quickly disable code highlighting for an inspection without opening the settings. Inspections have severities according to which they highlight code problems in the editor. To re-enable a suppressed inspection, delete the #pragma lines or // NOLINT comments. For example, when you suppress one of the Clang-Tidy inspections, modernize-avoid-bind, for a selected function, the following code appears above and below the declaration:Ĭlang-Tidy inspections have the additional Suppress for line option, which adds the // NOLINT comment, forcing Clang-Tidy to ignore the current line: You can also suppress inspections from the Results tool window.įor C/C++ code, CLion uses the #pragma clang diagnostic to suppress inspections. Suppress an inspection in the editorĬlick the arrow next to the inspection you want to suppress, and select the necessary suppress action. For example, syntax errors are always highlighted in the editor regardless of the settings. However, some inspections do not have this option. Most inspections in CLion can be suppressed. When you suppress an inspection, the code analysis engine doesn't highlight the problem found by this inspection in the specific piece of code (file, statement, function, or line). In the Inspection Results tool window (after running code analysis), right-click the inspection you want to disable and select Disable inspection.Ĭlick to hide the disabled inspection alerts. Place the caret at the highlighted line and press Alt+Enter (or click to use the intention action).Ĭlick the arrow next to the inspection you want to disable, and select Disable inspection.ĭisabling inspections in the Problems tool window Locate the inspection you want to disable, and clear the checkbox next to it. Press Ctrl+Alt+S to open the IDE settings and select Editor | Inspections. For example, syntax errors are always highlighted. However, some inspections will keep highlighting your code regardless of the settings. Most inspections in CLion can be disabled. Note that when you disable an inspection, you disable it in the current inspection profile it remains enabled in other profiles. It means that the code analysis engine stops searching project files for the problem that this inspection is designed to detect. When you disable an inspection, you turn it off. In this case, you can disable or suppress them. Some inspections may report problems that you currently do not want to see.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |