• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

umputun / agterm / 30124297746
98%

Build:
DEFAULT BRANCH: master
Ran 24 Jul 2026 08:33PM UTC
Jobs 1
Files 76
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

24 Jul 2026 08:30PM UTC coverage: 97.822% (+0.006%) from 97.816%
30124297746

push

github

web-flow
feat(keymap): allow arrow keys in chords (#291)

`parseKeybind` accepted only single-character keys plus tab/space/return/delete, so `map cmd+shift+left previous_session` failed with `invalid chord 'cmd+shift+left'` and no other spelling worked.

**What changed**

The four arrow names join the chord grammar, which lets the six actions that already ship on arrows (`focus_left_pane`, `focus_right_pane`, `previous_session`, `next_session`, and the two attention-nav ones) return their real chords from `BuiltinAction.defaultChord`. That removes the special case they needed: `arrowShortcut(for:)`, `arrowGlyphFallback`, and the `glyphHint` fallback are gone, so every keyed built-in resolves through one path. The generated starter `keymap.conf` also stops claiming `(no default)` for those six, which it did while their real chords lived only as hardcoded menu literals.

It closes a latent hole as well. The conflict checker resolves through `defaultChord`, so while the six returned nil their live chords were invisible to it, and `map cmd+opt+up new_session` would have silently double-bound the chord with no diagnostic.

A bare, modifier-less arrow is refused for `map`. A built-in becomes an always-on menu key equivalent with no text-field pass-through, so a bare arrow would swallow the key in the terminal, both palettes, the dashboard grid and every text field at once. Any modifier makes it bindable, and a bare non-arrow key stays legal as before.

The keyCode-to-name half of the `NSEvent` mapping moves into one host-free `namedKey(forKeyCode:)`. `CustomCommandRunner` and `UndoCloseShortcut` each carried their own copy, and a name the grammar accepts but a monitor cannot produce parses fine yet never fires; that exact failure shipped once already, for shifted symbols.

One behavior note worth knowing: widening the named-key set means a palette-only line whose shell command starts with a bare `up`/`down`/`left`/`right` now emits the same "must include a modifier... (continued)

36 of 36 new or added lines in 3 files covered. (100.0%)

5929 of 6061 relevant lines covered (97.82%)

4960547.73 hits per line

Jobs
ID Job ID Ran Files Coverage
1 30124297746.1 24 Jul 2026 08:33PM UTC 76
97.82
GitHub Action Run
Source Files on build 30124297746
  • Tree
  • List 76
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #30124297746
  • 30581c1c on github
  • Prev Build on master (#30113761782)
  • Next Build on master (#30135657501)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc