Default quake key ~ blocks typing tilde, and the shortcut is not listed in /hotkeys

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli, tooling

Research direction

Start by reading the default quake key in src/config.ts:9 and the terminal-input handling in src/index.ts:115 and ui.ts:171. Check how configured keys interact with pi.registerShortcut and the /hotkeys Extensions section. Done means the default avoids printable tilde input, expressible configured keys are discoverable, and the raw input tap remains for hiding while open.

Written by the indexing model from the issue text.

Description

Default quake keys are ["§", "~"] (src/config.ts:9). On a US keyboard there is no §, so ~ is the only default that works, and it makes the tilde impossible to type. That hurts, because ~ shows up constantly in paths (~/.pi/agent/...).

Setting quakeKeys in ~/.pi/agent/sidequest.json fixes it, so this is not a blocker. Two smaller things behind it though:

  1. The default could avoid a printable character. Something like f12 works everywhere and does not collide with any built-in pi binding.
  2. The key is grabbed with ctx.ui.onTerminalInput (src/index.ts:115), so it never appears in the Extensions section of /hotkeys. That table is built from pi.registerShortcut(key, { description }). Registering the shortcut when the configured key is expressible as a keybinding would make it discoverable, and would keep the raw input tap only for the hide-while-open path in ui.ts:171.
Dominant language
TypeScript
Stars
50
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from peterp/pi-sidequest

All issues in peterp/pi-sidequest

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.