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

Emit first key chord when timeout or wrong second key chord #15550

Closed
youdonghai opened this issue Nov 16, 2016 · 7 comments
Closed

Emit first key chord when timeout or wrong second key chord #15550

youdonghai opened this issue Nov 16, 2016 · 7 comments
Labels
feature-request Request for new features or functionality keybindings VS Code keybinding issues
Milestone

Comments

@youdonghai
Copy link

  • VSCode Version: 1.7.1
  • OS Version: Windows7

Steps to Reproduce:

  1. add new keyboard shortcut "; n"
  2. press ";"
  3. will wait for second key chord forever if I don't press any key
  4. press a wrong second key chord, nothing happen

Expected:

  1. at step 3 should have a timeout, when timeout the firset key ";" will input.
  2. at step 4, if a wrong second key press, like "m", then the ";m" will input to the editor.

Just like Atom did.

@ramya-rao-a ramya-rao-a added the keybindings VS Code keybinding issues label Nov 16, 2016
@alexdima
Copy link
Member

alexdima commented Dec 2, 2016

I believe our current chord behaviour is on par with Visual Studio (i.e. Visual Studio also waits without a timeout for a second chord part to be pressed).

@alexdima alexdima added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label Dec 2, 2016
@alexdima alexdima added this to the Backlog milestone Dec 2, 2016
@alexdima alexdima added the feature-request Request for new features or functionality label Apr 11, 2017
@alexdima alexdima removed their assignment Apr 11, 2017
@devinrhode2
Copy link

How can you change vs code to have a timeout on the second part of the chord?

@mjbvz mjbvz removed the *question Issue represents a question, should be posted to StackOverflow (VS Code) label May 16, 2018
@xaviergmail
Copy link

Any update on this? I currently use [Ctrl+A , H/J/K/L] "chords" but would love to have Ctrl+A triggered on its own if the none of the descending keybind sequences are triggered within a configurable threshold (~500ms?)

@web-rishi-shukla
Copy link

I need this feature too. Completely agree with @xaviergmail . Chords need to come with timeouts for second keystroke. In case of timeout, the first keystroke should be released/emitted to the Terminal/Editor window.

@alexdima
Copy link
Member

In the meantime, we have added a timeout of around 5s.

@Ahmad-Zaklouta
Copy link

In the meantime, we have added a timeout of around 5s.

can we control that? 5s is a lot of time

@web-rishi-shukla
Copy link

web-rishi-shukla commented Oct 24, 2021 via email

@github-actions github-actions bot locked and limited conversation to collaborators Dec 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality keybindings VS Code keybinding issues
Projects
None yet
Development

No branches or pull requests

8 participants