Remove conflicting keybindings to fix Ctrl+Shift+P Command Palette issue #181
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a critical usability issue where the Zephyr IDE extension was hijacking VS Code's default
Ctrl+Shift+P
keyboard shortcut for opening the Command Palette.Problem
When users pressed
Ctrl+Shift+P
with the Zephyr IDE extension enabled, instead of opening VS Code's Command Palette, the extension would trigger thezephyr-ide.flash
command and display the error message "RunZephyr IDE: West Update
first." This made it impossible to access the Command Palette using the standard keyboard shortcut.Root Cause
The extension defined conflicting keybindings in
package.json
:zephyr-ide.flash
bound toctrl+shift+p
(conflicted with Command Palette)zephyr-ide.build
bound toctrl+shift+B
(conflicted with VS Code's build shortcut)Solution
Completely removed the
keybindings
section frompackage.json
as suggested by the maintainer. This approach:Commands Affected
The following commands no longer have default keyboard shortcuts but remain fully functional:
Zephyr IDE: Build
(previouslyCtrl+Shift+B
)Zephyr IDE: Flash
(previouslyCtrl+Shift+P
)Users can access these commands via:
Ctrl+Shift+P
→ type "Zephyr IDE: Build" or "Zephyr IDE: Flash")Testing
Fixes #178.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.