#Keyboard reference

Bindings are grouped by where they work, because that is how they are learned. Inside the application, ? shows the same list, narrowed to the screen you are on.

Keys are fixed. Every action below has one binding, in every view, on every platform.

#The four tiers

L0 and L1 are complete alternatives to each other. Nobody is locked out for not knowing vim, and nobody who knows vim has to reach for an arrow key.

#Browse, filter, pin

Learn these three and you can build any view labdash can show. They are L0, so they sit in the footer wherever you are.

#Everywhere

The preview position has no key. auto puts the pane on the right at 120 columns or wider, and along the bottom below that.

#Sign in

#Browse

h and l walk the tree here instead of switching tabs, because Browse has no tabs to switch. It is the one context-dependent meaning in the whole keymap, and it is the universal tree convention.

#Merge requests

#Pipelines

#Job trace

w follows a growing log, which is the same verb as watching a running pipeline.

#To-Dos

#Coherence rules

Six rules cover the whole keymap. They are what let you guess a key you have not learned.

1. Lowercase acts on the row; uppercase escalates or reverses it. x closes, X reopens. d marks one done, D marks all. r refreshes one, Ctrl+R refreshes all.
2. A key means the same verb in every view. R retries. x stops. m makes it go: merge a merge request, or play a manual job. L shows logs. w keeps showing you a live thing. z collapses a group, a tree node, or a log section.
3. A key resolves to one action in the context you are in. Nothing is bound twice in the same view, so what you learned in one table still holds in the next.
4. n and N are search navigation only, and only while a search is live. That is why "new merge request" is Ctrl+N.
5. Esc goes back one level and q quits. Esc will not discard a half-typed comment without asking.
6. Chords are instantaneous. A chord is Ctrl-prefixed and lands on one keystroke. A g-then-g with a timeout produces mystery input on a slow SSH link.

#Reserved keys

#Markdown export

labdash keys --markdown > cheatsheet.md

The same content, from the same source, for pinning next to your monitor.

labdash keys --list

Every action name, one per line, for a bug report or a proposal to cite.