You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was generated using AI, if anything lacks clarity or context, please ask for clarification before starting work.
Summary
A bigger family of "shortcut" achievement ideas — Command Palette opened,
Quick Open / Go to File, Find & Replace opened, Rename Symbol, Go to
Definition, Format Document, Toggle Zen Mode, etc. Unlike paste (#16, via the
official Document Paste API), VS Code has no public "a command was
executed" event, so the only way to observe usage of a specific built-in
command is to contribute a package.json keybinding that shadows VS Code's
default binding for the same key, run the original command via vscode.commands.executeCommand(...), and increment a progression as a side
effect.
Why this is flagged exploratory, not ready-to-build
Collision risk with user rebinds. If a user has already remapped one of
these keys, our contributed keybinding either won't fire (if theirs takes
precedence) or double-fires/conflicts (depending on when clause
specificity) — unlike the paste API approach, which doesn't touch
keybindings at all.
Platform-specific bindings. Needs separate mac/key entries and when clauses matching VS Code's own defaults exactly (e.g. editorTextFocus), which differ per command and per OS.
Blast radius if wrong. A mistake here degrades a core editing shortcut
for every user of the extension, not just achievement tracking — much
higher stakes than any other listener in this codebase, all of which are
purely observational.
Suggested approach if pursued
Pilot with a single low-traffic, rarely-remapped command first — Rename
Symbol (F2) is a reasonable candidate — validate manually in the Extension
Development Host on macOS, Windows, and Linux, confirm the original command
still fires correctly and no keybinding regression occurs, before deciding
whether to build out the rest of the family.
Candidate commands
Command
Default keybinding
Command Palette
Ctrl+Shift+P / Cmd+Shift+P
Quick Open / Go to File
Ctrl+P / Cmd+P
Find & Replace
Ctrl+H / Cmd+Option+F
Rename Symbol
F2
Go to Definition
F12
Format Document
Shift+Alt+F / Shift+Option+F
Toggle Zen Mode
Ctrl+K Z / Cmd+K Z
Estimated effort: medium per command once the pattern is proven, plus a
non-trivial manual cross-platform validation pass before each ships.
Note
This issue was generated using AI, if anything lacks clarity or context, please ask for clarification before starting work.
Summary
A bigger family of "shortcut" achievement ideas — Command Palette opened,
Quick Open / Go to File, Find & Replace opened, Rename Symbol, Go to
Definition, Format Document, Toggle Zen Mode, etc. Unlike paste (#16, via the
official Document Paste API), VS Code has no public "a command was
executed" event, so the only way to observe usage of a specific built-in
command is to contribute a
package.jsonkeybinding that shadows VS Code'sdefault binding for the same key, run the original command via
vscode.commands.executeCommand(...), and increment a progression as a sideeffect.
Why this is flagged exploratory, not ready-to-build
these keys, our contributed keybinding either won't fire (if theirs takes
precedence) or double-fires/conflicts (depending on
whenclausespecificity) — unlike the paste API approach, which doesn't touch
keybindings at all.
mac/keyentries andwhenclauses matching VS Code's own defaults exactly (e.g.editorTextFocus), which differ per command and per OS.for every user of the extension, not just achievement tracking — much
higher stakes than any other listener in this codebase, all of which are
purely observational.
Suggested approach if pursued
Pilot with a single low-traffic, rarely-remapped command first — Rename
Symbol (F2) is a reasonable candidate — validate manually in the Extension
Development Host on macOS, Windows, and Linux, confirm the original command
still fires correctly and no keybinding regression occurs, before deciding
whether to build out the rest of the family.
Candidate commands
Ctrl+Shift+P/Cmd+Shift+PCtrl+P/Cmd+PCtrl+H/Cmd+Option+FF2F12Shift+Alt+F/Shift+Option+FCtrl+K Z/Cmd+K ZEstimated effort: medium per command once the pattern is proven, plus a
non-trivial manual cross-platform validation pass before each ships.