there actually a lot of issues about keyboard shortcut, but seems a year later, still there.
Hello,
Iām experiencing several issues related to custom keybindings and the general functionality of hotkeys. Below are the details:
Custom Keybinding for Closing Prompt Bar:
I set Ctrl + B as the keybinding to close the prompt bar using the following configuration in keybindings.json:{
"key": "ctrl+b",
"command": "aipopup.action.closePromptBar",
"when": "editorHasPromptBar && editorPromptBarFocused && editorTextFocus"
},
{
"key": "escape",
"command": "-aipopup.action.ā¦
opened 02:48AM - 23 Mar 24 UTC
There seems to currently be no way to hide the chat pane when the chat input fieā¦ ld has focus.
As described here: https://github.com/getcursor/cursor/issues/833#issuecomment-1772606399
I would like something like this to work:
```json
{
"key": "cmd+l",
"command": "workbench.action.toggleAuxiliaryBar",
"when": "auxiliaryBarFocus"
}
```
Interestingly the default shortcut for this ("cmd+alt+b") seems to work even when the chat input has focus. Maybe the "when" condition is wrong? I tried to figure it out using the ["inspect context keys"](https://code.visualstudio.com/api/references/when-clause-contexts#inspect-context-keys-utility) feature but that doesn't seem to work at all (don't print anything to the console).
opened 04:19PM - 21 Aug 24 UTC
closed 03:33AM - 01 Sep 24 UTC
recently switch back to cursor. This issue has actually been bothering me for a ā¦ long time since I started to use Cursor.
---
**Is your feature request related to a problem? Please describe.**
Since `cmd+k` is a lot of things from VS Code, so I changed the shortcut to `cmd+i` and `cmd+shift+i`, and I'm facing some unexpected behaviour.
Get used to the new shortcut is a little painful :(
because I use `delete line(cmd+shift+k)` often, and I have a combo shortcut `cmd+k {anykey}` as my own "key" shortcuts.
**Describe the solution you'd like**
there are two solutions I hope (personally prefer the first one):
- revert all `cmd+k` `cmd+shift+k` to VS Code default, and the Cursor open edit shortcut change to `cmd i` by default, just like Copilot inline chat did. Means totally replace the Copilot extension.
- **fix the shortcuts in open edit popup and terminal.**
**Additional context**
this video shows, I changed to shortcut to `cmd+i` and `cmd+shift+i`, I can do `open edit` with these shortcuts. But when focusing on the edit popup, I only can do toggle via old shortcut `cmd+k` or `cmd+shift+k`.
https://github.com/user-attachments/assets/ed839ff7-c75f-459e-b2e3-4080b45c192a
this video basically the same issue as above but for terminal
https://github.com/user-attachments/assets/57504de0-0ad8-4da9-9525-45c2738af58c
---
an old issue: #672
opened 10:57AM - 07 Jul 23 UTC
**Is your feature request related to a problem? Please describe.**
Right now thā¦ e prompt is bounded to cmd +k but there are lots of combination shortcuts which work with cmd +k. Like Fold all ((cmd + k ) + ( cmd + 0 ) )
**Describe the solution you'd like**
Use the different key combinations for the prompt.
**Additional context**
<img width="1728" alt="image" src="https://github.com/getcursor/cursor/assets/10386581/fc3fdddc-8926-4629-83e5-ceacf354b189">
opened 08:54PM - 25 Aug 24 UTC
**System Specifications:**
* **Cursor Version:** 0.39.6
* **VSCode Version:*ā¦ * 1.91.1
* **Commit:** a4f99b7dfb14460cb0bcebd9f6ac7ca158217920
* **Build Date:** 2024-08-19
* **Electron Version:** 29.4.0
* **Node.js Version:** 20.9.0
* **V8 Version:** 12.2.281.27-electron.0
* **Operating System:** Windows 11 (displayed as Windows_NT x64 10.0.22631)
Please note that while Iām using Windows 11, the system displays it as "Windows_NT x64 10.0.22631" due to the way the operating system versions are reported internally.
Hello,
Iām experiencing several issues related to custom keybindings and the general functionality of hotkeys. Below are the details:
1. **Custom Keybinding for Closing Prompt Bar:**
- I set `Ctrl + B` as the keybinding to close the prompt bar using the following configuration in `keybindings.json`:
```json
{
"key": "ctrl+b",
"command": "aipopup.action.closePromptBar",
"when": "editorHasPromptBar && editorPromptBarFocused && editorTextFocus"
},
{
"key": "escape",
"command": "-aipopup.action.closePromptBar",
"when": "editorHasPromptBar && editorPromptBarFocused && editorTextFocus"
}
```
- Although the prompt window indicates that "Ctrl+B" should close it (as shown in the attached screenshot, pressing `Ctrl + B` does not have any effect. The window still only closes using `Esc`.
<img src="https://github.com/user-attachments/assets/3cd5acf9-3d23-4c02-8438-ca9c27b01790" width="350">
2. **Hotkey Functionality Inside Prompt Bar and AI Chat:**
- When I am inside the prompt bar or chatting with the AI, none of the standard VS Code hotkeys seem to work. For instance:
- `Ctrl + Shift + P` does not bring up the Command Palette.
- Ctrl + ` (for switching to the terminal) is also unresponsive.
- Essentially, any hotkeys unrelated to the prompt or chat functionality become non-functional when either of these is active.
3. **Custom Hotkey for Chat Dropdown:**
- I attempted to change the `aichat.showchatdropdown` command from `Ctrl + Alt + L` to `Ctrl + Alt + M`. The UI reflects this change, as seen in the attached screenshot. However, pressing `Ctrl + Alt + M` does nothing, while the original `Ctrl + Alt + L` still works.
- The keybinding used is as follows:
```json
{
"key": "ctrl+alt+l",
"command": "-aichat.showchatdropdown"
},
{
"key": "ctrl+alt+m",
"command": "aichat.showchatdropdown"
}
```
- This suggests that the new keybinding isnāt being recognized correctly, and the command still defaults to the old keybinding.
<img src="https://github.com/user-attachments/assets/e810346a-cac1-4122-9ea5-35dfc786231a" width="350">
I would appreciate it if you could look into these issues.
_Please add the **bug** label to this issue if applicable_
4 Likes
+1
Still facing issues when copy pasting my keybindings.json from vscode to cursor
This is disappointing, the ability to customise keyboard shortcuts in VSCode is one of itās greatest assets, not being able to override cursors keyboard shortcuts is seriously a major decision factor pushing me to abandon a product I otherwise really like. Especially given Cursor teams decision to override some of VSCās default shortcuts that many users will have a decade of muscle memory built up.
Unless of course this is their admission to making a toy exclusively for new āvibe codersā?
(I pay for 4 team licences and >$1000 in token spend)
1 Like