# Breakpoints

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/ruby/2026.3/llms.txt).

Breakpoints are special markers that suspend program execution at a specific point. This lets you [examine the program state](examining-suspended-program.html) and [step through it](stepping-through-the-program.html).   Breakpoints can be simple, for example, suspending the program on reaching some line of code, or involve more complex logic, such as checking against [additional
conditions](#breakpoint_condition), [writing to a log](#log), and so on).

Once set, a breakpoint remains in your project until you remove it explicitly, except for [temporary breakpoints](#remove_once_hit).

> **Note:**
> If a file with breakpoints was modified externally, for example, updated through a VCS or changed in an external editor, and the line numbers have changed, breakpoints will be moved accordingly. Note that RubyMine must be running when such changes are made, otherwise they will pass unnoticed.

## Types of breakpoints

The following types of breakpoints are available in RubyMine:

* Line breakpoints: suspend the program upon reaching the line of code where the breakpoint was set. This type of breakpoints can be set on any executable line of code.

* Exception breakpoints: suspend the program when the specified Ruby exception is raised. Unlike stack traces, suspending an application on an exception allows you to examine the surrounding context or data while it is still available.

## Set breakpoints

Procedure: Set line breakpoints

* Click  the gutter at the executable line of code where you want to	set	the breakpoint. Alternatively, place the caret at the line and press `Ctrl+F8` (Windows), `⌘ F8` (macOS), `⌘ F8` (IntelliJ IDEA Classic (macOS)), `⌃ Quote` (macOS System Shortcuts), `Ctrl+F8` (XWin), `Ctrl+F8` (GNOME), `Ctrl+8` (KDE), `Ctrl+F8` (Emacs), `Ctrl+F8` (Sublime Text), `⌘ F8` (Sublime Text (macOS)), `F9` (Visual Studio), `F9` (Visual Studio (macOS)), `Ctrl+B` (TextMate), `Ctrl+F8` (NetBeans), `Ctrl+Shift+B` (Eclipse), `⌘ ⇧ B` (Eclipse (macOS)).

![Line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/rm_breakpoints_added.png)

* To set a temporary line breakpoint, press `Ctrl+Alt+Shift+F8` (Windows), `⌘ ⌥ ⇧ F8` (macOS), `⌘ ⌥ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⌥ ⇧ \` (macOS System Shortcuts), `Ctrl+Alt+Shift+F8` (XWin), `Ctrl+Alt+Shift+F8` (GNOME), `Ctrl+Alt+Shift+F8` (KDE), `Ctrl+Alt+Shift+F8` (Emacs), `Ctrl+Alt+Shift+F8` (Sublime Text), `⌘ ⌥ ⇧ F8` (Sublime Text (macOS)), `Ctrl+Alt+Shift+F8` (Visual Studio), `⌘ ⌥ ⇧ F8` (Visual Studio (macOS)), `Meta+Alt+Shift+F8` (TextMate), `Ctrl+Alt+Shift+F8` (NetBeans), `Ctrl+Alt+Shift+F8` (Eclipse), `⌘ ⌥ ⇧ F8` (Eclipse (macOS)). Alternatively, hold `Alt` (Windows), `Alt` (macOS), `Alt` (IntelliJ IDEA Classic (macOS)), `Alt` (macOS System Shortcuts), `Alt` (XWin), `Alt` (GNOME), `Alt` (KDE), `Alt` (Emacs), `Alt` (Sublime Text), `Alt` (Sublime Text (macOS)), `Alt` (Visual Studio), `Alt` (Visual Studio (macOS)), `Alt` (TextMate), `Alt` (NetBeans), `Alt` (Eclipse), `Alt` (Eclipse (macOS)) and click the gutter. This breakpoint will be removed from your project right after it is hit.

Procedure: Set exception breakpoints

1. Press `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Ctrl+Alt+B` (Visual Studio), `⌘ ⌥ B` (Visual Studio (macOS)), `Meta+Ctrl+B` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)) or select `Run | View Breakpoints` from the main menu.

2. In the Breakpoints dialog, press `Alt+Insert` (Windows), `⌘ N` (macOS), `⌃ N` (IntelliJ IDEA Classic (macOS)), `⌘ N` (macOS System Shortcuts), `Alt+Insert` (XWin), `Alt+Insert` (GNOME), `Alt+Insert` (KDE), `Alt+Insert` (Emacs), `Ctrl+N` (Sublime Text), `⌘ N` (Sublime Text (macOS)), `Ctrl+N` (Visual Studio), `⌘ N` (Visual Studio (macOS)), `Meta+Shift+N` (TextMate), `Alt+Insert` (NetBeans), `Alt+Insert` (Eclipse), `⌘ N` (Eclipse (macOS)) or click ![the Add button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.add.svg), and select     Ruby Exception Breakpoints  or JavaScript Exception Breakpoint .

![Creating an exception breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/rm_exception_breakpoint_setting.png)

3. In the  Choose Exception Class dialog, specify the exception class from a library or from your project.

## Manage breakpoints

Procedure: Remove breakpoints

* For non-exception breakpoints: click  the breakpoint in the gutter.

* For all breakpoints:   go to `Run | View Breakpoints` `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Ctrl+Alt+B` (Visual Studio), `⌘ ⌥ B` (Visual Studio (macOS)), `Meta+Ctrl+B` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)) in the main menu, select the breakpoint, and click  Remove or press `Delete` (Windows), `⌦` (macOS), `⌦` (IntelliJ IDEA Classic (macOS)), `⌦` (macOS System Shortcuts), `Delete` (XWin), `Delete` (GNOME), `Delete` (KDE), `Delete` (Emacs), `Delete` (Sublime Text), `⌦` (Sublime Text (macOS)), `Delete` (Visual Studio), `⌦` (Visual Studio (macOS)), `Delete` (TextMate), `Delete` (NetBeans), `Delete` (Eclipse), `⌦` (Eclipse (macOS)).

To avoid accidentally removing a breakpoint and losing its parameters, you can choose to remove breakpoints by dragging them to the editor or clicking the middle mouse button. To do this, go to `Settings | Build, Execution, Deployment | Debugger` and select Drag to the editor or click with the middle mouse button. Clicking a breakpoint will then [enable or disable](#disable) it.

Procedure: Mute breakpoints

If you don't need to stop at your breakpoints for some time, you can mute them. This allows you to resume normal program operation without leaving the debugger session. After that, you can unmute breakpoints and continue debugging.

* Click the Mute Breakpoints button ![Mute Breakpoints button](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.muteBreakpoints.svg) in the toolbar of the Debug tool window.

Procedure: Enable/disable breakpoints

When you remove a breakpoint, its [internal configuration](#breakpoint-properties) is lost. To temporarily turn an individual breakpoint off without losing its parameters, you can disable it:

* For non-exception breakpoints: right-click it  and set the Enabled option as required. Alternatively, you can do this by clicking a breakpoint while holding `Alt` (Windows), `Alt` (macOS), `Alt` (IntelliJ IDEA Classic (macOS)), `Alt` (macOS System Shortcuts), `Alt` (XWin), `Alt` (GNOME), `Alt` (KDE), `Alt` (Emacs), `Alt` (Sublime Text), `Alt` (Sublime Text (macOS)), `Alt` (Visual Studio), `Alt` (Visual Studio (macOS)), `Alt` (TextMate), `Alt` (NetBeans), `Alt` (Eclipse), `Alt` (Eclipse (macOS)) or clicking it with the middle mouse button. For the middle mouse button, check that removing breakpoints is not [assigned to it](#remove).

* For all breakpoints: click Run | View Breakpoints `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Ctrl+Alt+B` (Visual Studio), `⌘ ⌥ B` (Visual Studio (macOS)), `Meta+Ctrl+B` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)) and check/uncheck the breakpoint on the list.

Procedure: Move/copy breakpoints

* To move a breakpoint, drag it to another line.

* To copy a breakpoint, hold `Ctrl` (Windows), `Ctrl` (macOS), `Ctrl` (IntelliJ IDEA Classic (macOS)), `Ctrl` (macOS System Shortcuts), `Ctrl` (XWin), `Ctrl` (GNOME), `Ctrl` (KDE), `Ctrl` (Emacs), `Ctrl` (Sublime Text), `Ctrl` (Sublime Text (macOS)), `Ctrl` (Visual Studio), `Ctrl` (Visual Studio (macOS)), `Ctrl` (TextMate), `Ctrl` (NetBeans), `Ctrl` (Eclipse), `Ctrl` (Eclipse (macOS)) and drag a breakpoint to another line. This creates a breakpoint with the same parameters at the destination.

Procedure: View all set breakpoints

You can view the list of all breakpoints in the [Bookmarks](bookmarks.html) tool window. Breakpoints are automatically added to the dedicated list in the tool window once you place them in your code.

* In the main menu, go to `View | Tool Windows | Bookmarks` and expand the Breakpoints list.

![Bookmarks tool window](https://resources.jetbrains.com/help/img/idea/2026.3/rm_bookmarks-tool-window.png)

Procedure: Group breakpoints

You can organize breakpoints into groups, for example, if you need to mark out breakpoints for a specific problem.

* In the Breakpoints dialog `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+F8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Alt+F9` (Visual Studio), `⌥ F9` (Visual Studio (macOS)), `Meta+Shift+F8` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)), select a breakpoint you want to place in a group and select `Move to group` from the menu.

## Configure breakpoints' properties

Depending on the breakpoint type, you can configure additional properties which allow you to tailor its operation for specific needs. The most used options are available via [intentions](#intentions).

Procedure:

* To access breakpoint intentions, place the caret at the line with the breakpoint 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)), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Alt+Enter` (TextMate), `Alt+Enter` (NetBeans), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)). Use this option when you need to quickly configure basic breakpoint properties.

![Breakpoint intentions](https://resources.jetbrains.com/help/img/idea/2026.3/rm_debugger_breakpoints_intentions.png)

* To access the full list of properties, right-click the breakpoint and click More or press `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Ctrl+Alt+B` (Visual Studio), `⌘ ⌥ B` (Visual Studio (macOS)), `Meta+Ctrl+B` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)).

### Intentions reference

| Intention | Description |
| --- | --- |
|  Remove breakpoint  |  [Removes](#remove) the breakpoint at the selected line.  |
|  Disable Breakpoint  |  [Disables](#disable) the breakpoint at the selected line.  |
|  Edit Breakpoint  |  Opens a dialog with the most used breakpoint [properties](#properties). For more properties, click More or press `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Ctrl+Alt+B` (Visual Studio), `⌘ ⌥ B` (Visual Studio (macOS)), `Meta+Ctrl+B` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)).  |

### Breakpoints' properties reference

In this chapter, you can find information on the features available for breakpoints.

#### Enabled

Clear the checkbox to temporarily disable a breakpoint without removing it from the project. Disabled breakpoints are skipped during [stepping](stepping-through-the-program.html).

You can configure RubyMine to enable/disable breakpoints on clicking rather than removing them altogether. To do this, go to `Settings | Build, Execution, Deployment | Debugger` and set the Remove breakpoint option to Drag to the editor or click with middle mouse button.

#### Suspend execution

Specifies whether to pause the program execution when the breakpoint is hit.

Non-suspending breakpoints are useful when you need to log some expression without pausing the program (for example, when you need to know how many times a method was called) or if you need to create a trigger breakpoint that will enable [dependent breakpoints](#disable-until-hit) when hit.

#### Condition

This option is used to specify a condition that is checked each time the breakpoint is hit. A condition is a Ruby Boolean expression evaluating to `true` or `false`, for example `@user.name == "Example User"`.  If the condition evaluates to `true` , the selected actions are performed. Otherwise, the breakpoint is ignored.

> **Note:**
> The condition must be valid at the line where the breakpoint is set.

The result of the expression is taken from the return statement. When there is no return statement, the result is taken from the last line of code.

When evaluating expressions, make sure you are aware of their possible side effects as they may potentially affect the behavior and the result of the program.

#### Logging options

When a breakpoint is hit, the following can be logged to the console:

* "Breakpoint hit" message: a log message like `Breakpoint reached at ocean.Whale.main(Whale.java:5)`.

* Stack trace: the stack trace for the current frame. This is useful if you want to check what paths have led to this point without interrupting the program execution.

* Evaluate and log: the result of an arbitrary expression. The result of the expression is taken from the return statement. When there is no return statement, the result is taken from the last line of code, which doesn't have to be an expression: a literal works too. This can be used to produce a custom message or to keep track of some values as the program executes. When evaluating expressions, make sure you are aware of their possible side effects as they may potentially affect the behavior and the result of the program.

Procedure: Set a logging breakpoint

1. (optional) If the expression that you want to log is in front of you in the editor, select	it.

2. Hold `Shift` (Windows), `Shift` (macOS), `Shift` (IntelliJ IDEA Classic (macOS)), `Shift` (macOS System Shortcuts), `Shift` (XWin), `Shift` (GNOME), `Shift` (KDE), `Shift` (Emacs), `Shift` (Sublime Text), `Shift` (Sublime Text (macOS)), `Shift` (Visual Studio), `Shift` (Visual Studio (macOS)), `Shift` (TextMate), `Shift` (NetBeans), `Shift` (Eclipse), `Shift` (Eclipse (macOS)) and click the gutter.

#### Remove once hit

Specifies whether the breakpoint should be removed from the project after it has been hit once.

#### Disable until hitting the following breakpoint

When a breakpoint is selected in the Disable until hitting the following breakpoint box, it acts as a trigger for the current breakpoint. This [disables](#enabled) the current breakpoint until the specified breakpoint has been hit.

You can also choose whether to disable it again after this has happened or leave it enabled.

This option is useful when you only need to suspend the program under certain conditions or after certain actions. In this case, the trigger breakpoint usually isn't required to stop the program execution and is made [non-suspending](#suspend_policy).

## Breakpoint statuses

Breakpoints can have the following statuses:

|  Status  |  Description  |
| --- | --- |
|  Verified  |  After you have started a debugger session, the debugger checks whether it is technically possible to suspend the program at the breakpoint. If yes, the debugger marks the breakpoint as verified.  |
|  Warning  |  If it is technically possible to suspend the program at the breakpoint, however there are issues related to it, the debugger sets the breakpoint status to warning. This may happen, for example, when it is impossible to suspend the program at one of the method's implementations.  |
|  Invalid  |  If it is technically impossible to suspend the program at the breakpoint, the debugger marks it as invalid. This often happens because there is no executable code on the line.  |
|  Inactive/dependent  |  A breakpoint is marked as inactive/dependent when it is [configured 						to be disabled until another breakpoint is hit](#disable-until-hit), and this has not happened yet.  |
|  Muted  |  All breakpoints are temporarily inactive because they have been [muted](#mute).  |
|  Disabled  |  This breakpoint is temporarily inactive because it has been [disabled](#disable).  |
|  Non-suspending  |  The [suspend policy](#suspend_policy) is set for this breakpoint so that it does not suspend the execution when hit.  |

## Breakpoint icons

Depending on their [type](#breakpoint-types) and [status](#breakpoint-statuses), breakpoints are marked with the following icons:

|  | Line | Exception |
| --- | --- | --- |
|  Regular  |  ![line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_set_breakpoint.svg)  |  ![exception breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_exception_breakpoint.svg)  |
|  Disabled  |  ![disabled line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_disabled_breakpoint.svg) |  ![disabled exception breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_disabled_exception_breakpoint.svg)  |
|  Verified  |  ![verified line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_verified_breakpoint.svg)  |  |
|  Muted  |  ![muted line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_muted_breakpoint.svg)  |   |
|  Inactive/dependent  |  ![inactive/dependent line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_dep_line_breakpoint.svg)  |  |
|  Muted disabled  |  ![muted disabled line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_muted_disabled_breakpoint.svg)  |  |
|  Non-suspending  |  ![non-suspending line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_no_suspend_breakpoint.svg)  |  |
|  Verified non-suspending  |  ![verified non-suspending line breakpoint](https://resources.jetbrains.com/help/img/idea/2026.3/app.debugger.db_verified_no_suspend_breakpoint.svg)  |  |
|  Invalid  |

> **Note:**
> The provided icons correspond to the standard IDE themes. Custom themes may use different icons.

## Productivity tips

Use breakpoints for "printf" debugging
: Use [non-suspending](#suspend_policy) [logging](#log) breakpoints (sometimes referred to as watchpoints in other debuggers) instead of inserting print statements in your code. This provides a more flexible and centralized way of handling debug log messages.

Set logging breakpoints more quickly
: To set a [non-suspending](#suspend_policy) [logging](#log) breakpoint, hold `Shift` (Windows), `Shift` (macOS), `Shift` (IntelliJ IDEA Classic (macOS)), `Shift` (macOS System Shortcuts), `Shift` (XWin), `Shift` (GNOME), `Shift` (KDE), `Shift` (Emacs), `Shift` (Sublime Text), `Shift` (Sublime Text (macOS)), `Shift` (Visual Studio), `Shift` (Visual Studio (macOS)), `Shift` (TextMate), `Shift` (NetBeans), `Shift` (Eclipse), `Shift` (Eclipse (macOS)) and click the gutter. This will not suspend the program execution and instead log a message like   `Breakpoint reached` . If you want to log some expression that is in front of you in the editor, select it before holding `Shift` (Windows), `Shift` (macOS), `Shift` (IntelliJ IDEA Classic (macOS)), `Shift` (macOS System Shortcuts), `Shift` (XWin), `Shift` (GNOME), `Shift` (KDE), `Shift` (Emacs), `Shift` (Sublime Text), `Shift` (Sublime Text (macOS)), `Shift` (Visual Studio), `Shift` (Visual Studio (macOS)), `Shift` (TextMate), `Shift` (NetBeans), `Shift` (Eclipse), `Shift` (Eclipse (macOS)) and clicking the gutter.

Add breakpoint descriptions
: If you have many breakpoints in your project, you can add descriptions to breakpoints for ease of search. To do this, right-click a breakpoint in the Breakpoints dialog `Ctrl+Shift+F8` (Windows), `⌘ ⇧ F8` (macOS), `⌘ ⇧ F8` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ F8` (macOS System Shortcuts), `Ctrl+Shift+F8` (XWin), `Ctrl+Shift+F8` (GNOME), `Ctrl+Shift+F8` (KDE), `Ctrl+Shift+F8` (Emacs), `Ctrl+Shift+F8` (Sublime Text), `⌘ ⇧ F8` (Sublime Text (macOS)), `Alt+F9` (Visual Studio), `⌥ F9` (Visual Studio (macOS)), `Meta+Shift+F8` (TextMate), `Ctrl+Shift+F8` (NetBeans), `Ctrl+Shift+F8` (Eclipse), `⌘ ⇧ F8` (Eclipse (macOS)) and select Edit description from the menu. Now when you start typing the breakpoint name, it gets the focus.

Jump to source
: To jump from the Breakpoints dialog to the line of code where the selected breakpoint is set, press `F4` (Windows), `⌘ ↓` (macOS), `F4` (IntelliJ IDEA Classic (macOS)), `F4` (macOS System Shortcuts), `F4` (XWin), `F4` (GNOME), `F4` (KDE), `F4` (Emacs), `F4` (Sublime Text), `F4` (Sublime Text (macOS)), `F4` (Visual Studio), `⌘ ↓` (Visual Studio (macOS)), `F4` (TextMate), `F4` (NetBeans), `F12` (Eclipse), `F3` (Eclipse (macOS)).

