# Fix problems

By default, CLion analyzes the code in all open files and highlights the detected code issues. You can fix most of the issues immediately by [applying quick-fixes](intention-actions.html).

Place the caret at the highlighted piece of code and press `Alt+Enter` (Windows), `⌥ ⏎` (macOS), `⌥ ⏎` (IntelliJ IDEA Classic (macOS)), `⌥ ⏎` (macOS System Shortcuts), `Alt+Enter` (XWin), `Alt+Enter` (GNOME), `Alt+Enter` (KDE), `Alt+Enter` (Emacs), `Alt+Enter` (Sublime Text), `⌥ ⏎` (Sublime Text (macOS)), `⌥ ⏎` (Xcode), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Alt+Enter` (ReSharper), `⌥ ⏎` (ReSharper (macOS)), `Alt+Enter` (QtCreator), `⌥ ⏎` (QtCreator (macOS)), `Alt+Enter` (NetBeans), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)):

![Applying a quick-fix in the editor](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspection_fix.png)

You can also hover over the highlighted element and apply a quick-fix from the inspection popup:

![Applying a quick-fix in the editor](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspection_fix_popup.png)

For some inspections, you can open a preview by pressing `Ctrl+Shift+I` (Windows), `⌥ Space` (macOS), `⌘ ⇧ I` (IntelliJ IDEA Classic (macOS)), `⌘ Y` (macOS System Shortcuts), `Ctrl+Shift+I` (XWin), `Ctrl+Shift+I` (GNOME), `Ctrl+Shift+I` (KDE), `Ctrl+Shift+I` (Emacs), `Ctrl+Shift+I` (Sublime Text), `⌥ Space` (Sublime Text (macOS)), `⌃ F1` (Xcode), `Alt+F12` (Visual Studio), `⌥ Space` (Visual Studio (macOS)), `Ctrl+Shift+I` (ReSharper), `⌥ Space` (ReSharper (macOS)), `Ctrl+Shift+I` (QtCreator), `Ctrl+Shift+I` (QtCreator (macOS)), `Ctrl+Shift+I` (NetBeans), `Ctrl+Shift+I` (Eclipse), `⌥ Space` (Eclipse (macOS)).

If you [perform code analysis](running-inspections.html) or [execute a single inspection](running-inspections.html#run-one-inspection) in a larger scope of source files, CLion displays the detected code issues in the [Problems tool window](problems-tool-window.html). When you select a specific issue in this window, its report is shown in the right part of the window.

> **Tip:**
> * To display the source code of an issue in the editor, when it is selected in the [Problems tool window](problems-tool-window.html), toggle the Navigate with Single Click ![Navigate with Single Click](https://resources.jetbrains.com/help/img/idea/2026.2/app.general.autoscrollToSource.svg) button.
>
> * If you find that some of the reported issues are minor or not helpful to you, you can ignore them either by [disabling](disabling-and-enabling-inspections.html) the corresponding inspection or by [suppressing](disabling-and-enabling-inspections.html#suppress-inspections) it in a specific piece of code.

Procedure: Apply quick-fixes from inspection results

In the [Problems tool window](problems-tool-window.html), select the issue and do one of the following:

* If CLion suggests any fixes to the issue as described above, you can use one of them to fix the problem immediately:

![Quick-fixes for inspection results](https://resources.jetbrains.com/help/img/idea/2026.2/cl_resolveProblems.png)

You can also batch-apply quick fixes for several issues at a time. Click Fix partially in the results description tab:

![Applying quick-fixes to several inspection results](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspections_results_fixpartially.png)

Alternatively, you can select several issues and choose a proper quick-fix from the context menu.

* If no resolutions are suggested, use the `Jump to source` command in the context menu and fix the problem manually.

## Export results

After you run inspections, results are displayed on a dedicated tab of the Problems tool window. You can export them to one of the available formats.

Procedure:

1. In the Problems tool window (`View | Tool Windows | Problems` or `Alt+6` (Windows), `⌘ 6` (macOS), `⌘ 6` (IntelliJ IDEA Classic (macOS)), `⌘ 6` (macOS System Shortcuts), `Alt+6` (XWin), `Alt+6` (GNOME), `Alt+6` (KDE), `Alt+6` (Emacs), `Alt+6` (Sublime Text), `⌘ 6` (Sublime Text (macOS)), `Alt+6` (Xcode), `Alt+6` (Visual Studio), `⌘ 6` (Visual Studio (macOS)), `Alt+6` (ReSharper), `⌘ 6` (ReSharper (macOS)), `Alt+1` (QtCreator), `⌘ 1` (QtCreator (macOS)), `Alt+6` (NetBeans), `Alt+6` (Eclipse), `⌘ 6` (Eclipse (macOS))), switch to the tab that contains the inspection results that you want to export and click ![the Export button](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.export.svg).

![The Export button in the Inspection Results tool window](https://resources.jetbrains.com/help/img/idea/2026.2/cl_export_inspection_results.png)

2. Select the format in which you want to save the report:  HTML   or  XML .

3. Specify the target directory and click Save.

## See also

### Concepts

[Static code analysis](code-inspection.html)

### How tos

[Intention actions](intention-actions.html)

### Reference

[Problems tool window](problems-tool-window.html)