Open matthiasgeihs opened 3 months ago
Hi @matthiasgeihs! Thank you for this feedback. I would recommend re-mapping the shortcut to something that works better for you. While I'm sure this was frustrating, we've learned (through tons of trial and error before eventually landing here) that there is no shortcut that is both ergonomic and won't bother at least some subset of users. We've taken what we believed to be the best route and don't plan to change right now.
You're right about the hardcoding and this definitely isn't ideal. It doesn't look like there's any reliable way of getting the list of keyboard shortcuts for commands from the VS Code extension API, so we may be stuck showing the default value
fair enough, i'll leave it open for a bit, to see if others encounter a similar problem, or want to add to the discussion here. feel free to close this any time you feel appropriate.
+1
+1 I find it super frustrating to have to change the default workflow when a new extension is added and remaps a default shortcut. My beef is with CMD + SHIFT + L to add a cursor to all instances of a selection.
How would one remap the shortcut in Continue to something else? Have tried looking for documentation but couldn't seem to find it, sorry!
I've had to disable Continue for now 😿
+1 for same reasons as described by previous users and changing the default vscode shortcuts is not an option for me.
Validations
Problem
Cmd+L is the default shortcut for line selection, which I use frequently. Having Continue overwrite this shortcut doesn't work for me.
Moreover, the shortcut seems to be hardcoded in a couple of places. When I set a different shortcut, the tooltip hints will still mention Cmd+L as the shortcut (even though this is not longer true).
Solution
I'd prefer a different default shortcut for adding current selection to the chat context, e.g., Cmd+Shift+I.