Keyboard Shortcuts

Leed’s shortcuts belong to the page body. They are the editor’s keymap, not the application’s: they fire when your cursor is inside the text you are writing, and nowhere else. Clicking into the title field, the right rail, a settings screen or the rail itself takes you out of their reach — with one exception, covered at the end.

To see the list without leaving the page, put your cursor in the body and press Cmd + Shift + ? on a Mac, Ctrl + Shift + ? elsewhere — or just F1, which is bound to the same dialog and needs no modifiers.

Throughout the product, and throughout this page, Mod is the platform’s own command key.

The dialog lays the same five groups out in two columns — Editor, Formatting and Blocks on the left, Lists and Navigation on the right. The sections below follow that order so the page and the app agree.

Editor

Formatting

Blocks

Lists

Navigation

These four are the least self-explanatory in the dialog, so here is what each is actually for.

Four shortcuts the dialog does not list

All four are bound and all four work. They are simply missing from the in-app list, which is a gap in the product rather than in these docs.

Outside the editor

One shortcut lives somewhere else. On the Settings home screen, Cmd / Ctrl + K focuses the card search box, so you can jump from anywhere in Settings to the card you want by typing its name.

When a shortcut does nothing

Three reasons, in the order they are likely.

Your cursor is not in the page body. This is nearly always it. Every shortcut on this page except the settings search is registered inside the editor, so it only fires when the editor has focus. Click into the body text and try again.

The page is read-only. A page you are viewing rather than editing — because it is published and locked, because someone else holds the edit lock, or because you have switched into Viewing mode — will not take a cursor in the body, so nothing types and no shortcut fires. Autosave, collaboration and locking explains the publish lock, and suggesting mode and tracked changes covers Viewing mode.

You are looking for a button that a page-type setting hides. A posts-type page type can switch formatting features off, which removes their toolbar buttons. Note what that does and does not do: it hides the control, it does not unbind the key. Of everything in the dialog, only Code block corresponds to one of those switchable features, and pressing ⌘⇧{ still inserts a code block on a page type where the toolbar button has been removed. What each page type lets you format has the nine switches and where each one bites — and note that documentation and api page types are not gated at all, so a docs author hunting for a switch that turned something off will not find one.

Every shortcut here has a toolbar button behind it, and the editor toolbar reference pairs each control with the Leed Markdown it produces — the fastest way to work out which shortcut you actually wanted.