Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Shortcuts with numpad keys show as "Ctrl+num1" and "⌃NUMADD"

Open Beginner friendly
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
electron, react, typescript

Research direction

Start with formatAccelerator in src/shared/accelerator.ts and the existing cases in tests/accelerator.test.ts; compare the macOS and Windows formatting paths for numpad names and longer keys. Add coverage for numpad keys on both platforms, preserve uppercase single letters and the case of longer names, then run pnpm test.

Written by the indexing model from the issue text.

Description

bug good first issue

You can record a shortcut that uses the numeric keypad, but Settings, the tray menu and the empty shelf then show Electron's internal key names:

Recorded macOS shows Windows and Linux show
Control + keypad 1 ⌃NUM1 Ctrl+num1
Control + keypad + ⌃NUMADD Ctrl+numadd
Control + Insert ⌃INSERT Ctrl+Insert
Where to look
  • src/shared/accelerator.ts: formatAccelerator. On macOS it upper-cases any key it has no symbol for, which is meant for single letters (v → V) but also catches num1 and Insert. keyFromCode shows every numpad name it can record: num0–num9, numadd, numsub, nummult, numdiv and numdec
  • tests/accelerator.test.ts: the formatAccelerator tests
Done when
  • Numpad keys read as something like Num 1 and Num + on every platform, so ⌃Num 1 and Ctrl+Num +. If you prefer another readable form, explain it in the pull request
  • Longer key names keep their own case on macOS (⌃Insert, ⌃F13), while single letters are still upper-cased
  • Tests cover numpad keys on macOS and Windows, and pnpm test passes

Suggested pull request title: fix(settings): show numpad keys readably in shortcuts


New to OpenPaste? CONTRIBUTING.md covers setup, the code conventions and the checks to run before a pull request (pnpm typecheck, pnpm test, pnpm format, pnpm cleaner). Leave a comment if you're picking this up so nobody doubles up.


Generated by Claude Code

Dominant language
TypeScript
Stars
0
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

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 alexsilver8/openpaste

All issues in alexsilver8/openpaste

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.