Keyboard shortcuts

Revue is built to be driven from the keyboard: you can go through a whole review, from the list to the last file, without touching the mouse. You don't have to learn this page by heart. Two things in the app show you the keys:

• Hold Alt (Cmd on macOS) for a moment: every button and tab on screen that has a shortcut gets a small badge with its key. Let go and they disappear.
• Press Ctrl+/ (Cmd+/ on macOS), or click Hold Alt for shortcuts at the right end of the status bar, for the Keyboard shortcuts list. In a pull request, ? opens it too.

How to read this page#

• Ctrl in the Windows, Linux column becomes Cmd on macOS when the macOS column says so. Keys written only once (like Ctrl+Tab) are the same on every system, macOS included.
• Single-letter keys (j, n, v …) work only while you're not typing. As soon as a text field, a search box or a comment box has the cursor, the letters go into the text. Press Esc to leave the field and the shortcuts work again.
• Keys that use Ctrl, Cmd or a function key work while typing too, unless the table says otherwise.

Everywhere#

These work in any view of the main window.

Advanced: details of the global keys

• Tab order. Ctrl+Tab goes through the open tabs (What's new, pull requests, repositories, tickets, Settings), never the Pull requests or Repositories pages. Settings → Behavior → Tab switching picks the order: Visual order (left to right as in the tab bar, wrapping around; the default) or Last used (back to the previous tab; press Tab again while still holding Ctrl to go further back).
• Closing tabs. Ctrl+W closes the Settings or What's new tab, a ticket, a repository or a pull request, whichever is on screen. A pinned tab (right-click a tab for Pin tab / Unpin tab) isn't closed: Revue says Pinned tab: unpin it to close it.
• Light and dark. Ctrl+Shift+T switches to the opposite of what's on screen. If the theme was set to As the system, it stops following the system.
• Text size steps through the sizes Settings → Appearance → Text offers for the interface: 80, 90, 100, 110, 125 and 150 %. The code's own size isn't changed by these keys.
• Back and forward on Windows and Linux work even while a text field has the cursor. On macOS, inside a text field Option+← / → move the cursor by a word instead (except in the Code tab, where they walk your jumps).
• Ctrl+J does nothing until a Jira site is connected.

The pull request list#

On the Pull requests page. The same keys work on the Repositories and Projects pages, for their rows.

See The pull request list, tabs and search for the list itself.

A pull request#

These work in an open pull request, whichever of its tabs is on screen, while you're not typing.

Tabs#

The number keys pick the pull request's tabs by their position, left to right.

The PR stack tab only shows when the pull request is part of a stack (see Stacked pull requests), and Slack threads only with Slack connected (see Slack).

Moving through the diff#

At the last change, n says Last change: again to go to the first; pressing it again wraps around to the first one.

Inside the diff#

Once you've clicked into the diff's code, it takes these keys:

Which changes you see#

Layout#

Comments and the review#

Search and files#

The PR stack tab#

Advanced: when these keys don't fire

• All single-key shortcuts in a pull request are off while any text field in it has the cursor: a comment box, a reply, the find bar, a filter. Ctrl/Cmd combinations still work.
• Ctrl+↓ / ↑ follow the same rule in the Files tab; in the Code tab they work even with the cursor in the code (see The Code tab).
• Changes in files Revue holds back as ignored (see Reviewing the diff) are skipped by n / p; folded files are passed over.
• t and b in focus mode bring a sidebar back for this visit only; outside focus mode b is remembered for every pull request.
• - and + do nothing outside focus mode.
• Esc works in steps: a selected line range is cleared first, then an open search closes, then (in focus mode) focus mode ends.

A repository#

In a repository tab (opened from Repositories, Ctrl+G), while you're not typing.

With the mouse: Shift+click a second commit to see the range of commits between them; double-click a branch to switch to it; double-click a commit in Graph to open it in Commits. See Repositories and branches.

The Code tab#

In a pull request's or repository's Code tab. See Browsing code.

Right-click in the code for Go to Definition, Find References, Show in Files (the PR's diff) (on a line the pull request changed), Copy and Select All.

With the mouse: a click on a file in the tree opens it in place of the last file you didn't keep; a double-click keeps it open as a tab. Middle-click a file tab to close it.

Find in Files#

The Find in Files dialog (Ctrl+Shift+F, Cmd+Shift+F on macOS). The arrows and Enter work while you type in its fields.

The same list, with the same keys, shows the results of Find References and of a definition found in several places.

The search palette and Go to file#

The palette (Ctrl+K) and the Go to file picker (Ctrl+P) share their keys:

Type Focus mode in the palette to find the focus mode command, and What's new (or Changelog) for what changed in each version of Revue (see Updates).

Comment boxes and text editors#

In any comment, reply, review or description box (the Markdown editor):

Emoji and channel suggestions#

Type : and at least two letters of an emoji's name (:thu) and a list of matching emoji pops up under the cursor. In a box that posts to Slack, the list holds the workspace's emoji too; type # and a letter to get Slack channels.

Advanced: when the emoji list appears

• The : has to start a word: after a space, at the start of the text, or after (, [, {, " or '. So 10:30 and :) never ask.
• Nothing pops up while text is selected, or in the Preview tab.

Ordinary text editing#

Text fields and editors use the usual keys of your system:

Moving and selecting by word, and by the parts of a word, take other keys in Settings → Keyboard shortcuts (under Comments and editor), like any shortcut there.

All text editing keys

Windows, Linux	macOS	What it does
Ctrl+] / Ctrl+[	Cmd+] / Cmd+[	Indent / outdent the line
Shift+Home / Shift+End	the same, or Cmd+Shift+← / →, or Ctrl+Shift+A / E	Select to the start / end of the line
Ctrl+Shift+Home / End	Cmd+Shift+↑ / ↓	Select to the start / end of the text
—	Ctrl+A / Ctrl+E	Start / end of the line
—	Cmd+Backspace / Cmd+Delete	Delete to the start / end of the line
Linux: Shift+Alt+↑ / ↓; Windows: Ctrl+Alt+↑ / ↓	Cmd+Option+↑ / ↓	Add a cursor above / below (in the code editor)
Ctrl+D	Cmd+D	Select the next occurrence of the selection, as another selection (the word at the cursor first); typing then changes every one. Also Select Next Occurrence in the right-click menu (in the composer and the code editor)
Ctrl+.	Cmd+.	Code actions, in an editor that has them
Ctrl+H	Cmd+Shift+F	Replace, in an editable editor with a search bar
—	Ctrl+Cmd+Space	The character viewer (emoji and symbols)

A shortcut that a text field uses itself wins while that field has the cursor: for example Ctrl+B makes text bold in a comment box instead of going to the list.

Settings#

On the Settings tab, while you're not typing:

Dialogs and confirmations#

Small confirmations pop up as a bubble from the button you clicked (for example before deleting something). In a bubble:

• Enter or Space press the focused button. For something destructive the focus starts on Cancel, so an accidental Enter does nothing harmful.
• Tab or the arrow keys move to the other button.
• Esc, or a click anywhere outside, cancels.

The mouse#

Shortcut badges#

Hold Alt alone (on macOS Cmd, because Option types characters there) for a short moment. Each button and tab on screen that has a shortcut shows its keys in a badge at its corner. Nothing on the screen moves.

The badges disappear as soon as you let go, press another key, click, or leave the window. The short wait before they appear keeps them from flashing when you press Alt+← and the like.

Advanced: how badges are placed

• A badge sits at its control's corner when there's room, else beside it with a thin line to it, never on top of another badge and always inside the window.
• When badges are crowded or moved away from their control, each gets its own colour (the badge's border, its line and a ring around the control), so you can tell which belongs to which.
• Tabs show their number badge at the top-left corner, because the top-right holds their counts.
• On macOS the labels use the system's symbols: ⌘ for Cmd, ⌥ for Option, ⌃ for Ctrl, ⇧ for Shift.