Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant' remap ctrl+a/b/f/h/e in find widget? #211350

Open
tmpm697 opened this issue Apr 25, 2024 · 1 comment
Open

Cant' remap ctrl+a/b/f/h/e in find widget? #211350

tmpm697 opened this issue Apr 25, 2024 · 1 comment
Assignees

Comments

@tmpm697
Copy link

tmpm697 commented Apr 25, 2024

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: Version: 1.88.1
  • OS Version: macos ventura 13.6.6

Steps to Reproduce:

try to remap ctrl+b to cmd+b as follow:

    {
        "key": "cmd+b",
        "command": "-workbench.action.toggleSidebarVisibility"
    },
    {
        "key": "cmd+b",
        "command": "cursorLeft",
        "when": "textInputFocus"
    },

expecting that when focus find widget, press cmd+b will move cursor back one character --> but it does not work.

this breaks my current workflow that does not favor ctrl meta key.

I tried this with cmd+a, also not work:

    {
        "key": "cmd+a",
        "command": "vscode-neovim.send",
        "when": "findInputFocussed",
        "args": "<C-a>"
    },

expecting cmd+a in find widget will move to start of pattern in find input box.

@tmpm697
Copy link
Author

tmpm697 commented Apr 26, 2024

This issue also seems to apply when you are in inQuickOpen

so whatever when you're in something that need user input, it's all default to use ctrl instead of allowing user to change it to like cmd+<..> for nevigating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants