Back to Blog
Features
October 31, 2026
Max Binshtok•nash Core Team

Preview: Find and Edit Keyboard Shortcuts in Nash 0.13.7

A shortcut is only useful if you know what it actually runs. This is a preview of the Keyboard Shortcuts editor coming in Nash 0.13.7, ahead of its November 13 release. It brings discovery, conflict explanations, and editing into one view rather than making you compare configuration files.

Find the Binding That Wins

Open Keyboard Shortcuts with SUPER+Alt+K (⌘⌥K on macOS), or choose it from the command palette. Search by title, command ID, or description. For a key search, try cmd+t, ctrl shift, or f5. Use @conflict pane to narrow the list to ineffective pane shortcuts; @changed and @unbound help you review overrides and commands without keys.

Bindings identify their source: Default, User, or Lua. A shortcut that does nothing explains why: another command wins, Lua disables it, or the leader key takes it. Lua bindings take priority over commands and tasks. Notes also explain when an active key table gets a key first.

To investigate a physical keypress, press Alt+K inside the view, then the key. Nash shows what runs now, including Lua bindings, or whether the key is free and reaches the program in your pane.

Change a Key With the Consequences Visible

Select a row and press Enter, then press your proposed shortcut. Nash checks it before writing anything. A free key offers Save; one owned by another command or task offers Move here, and Swap when replacing a key and the other entry can safely use your old one.

Moving removes that key from other entries that list it. Swapping is not promised for every conflict: Lua bindings, the leader key, and competing bindings can prevent it. Those Lua and leader conflicts must be resolved outside this edit. Bare typing or editing keys get a warning because they would stop reaching pane programs.

For example, search for a command, select its current shortcut, record a preferred combination, and review the choices before confirming. Shift+Enter adds another shortcut instead of replacing one; Ctrl+R resets an entry to Nash's defaults.

Keep Your Files and Know the Boundaries

The editor changes only keys in your user commands.toml and tasks.toml. Comments, entry order, and unrelated formatting stay intact. Saved changes reload immediately in every window, including the palette and menu bar.

Lua rows are read-only. Key tables, mouse bindings, and key sequences are outside the editor, and project .nash.toml task keys cannot be changed here. Keys intercepted by the operating system cannot be recorded. This is a focused editor for command and task shortcuts, not a replacement for every input setting.