-
Notifications
You must be signed in to change notification settings - Fork 57
Allow chords #17
Comments
👍 |
Yeah, I really want to type 'j k' to escape from insert mode. |
👍 This would be a great reason to switch to atom from my evil-mode key-chord-mode enabled emacs. |
This is the only think keeping me from using Atom regularly. Can we get an update on the status of this feature? |
There's been no progress as I am currently occupied with performance issues and solidifying the API. If anyone would like to submit a PR and link it to this issue I'd be happy to review it. |
This would be great to have. When something as fundamental as text input stalls it really breaks apart the developer experience between him and his work. Might as well have someone shove a piece of paper in front of your monitor every so often. Then as soon as you have an identifier beginning with |
I don't suppose there's a plan for this to make it into the 1.0 release, is there? It's really the last thing keeping me away from atom. |
It sounds like many people following this issue are actually interested in key bindings for sequences like These kinds of sequences will be supported correctly in the next Atom release. Chords, where multiple printable character keys are hit simultaneously, are still not supported. |
+1 for sequence chords. (i.e. "ctrl-d, e", where you hold down "ctrl", and then type "d", and "e" sequentially, for example. -- it's a nice way to group related functionality under a root key.) |
+1 for @BrainSlugs83's described sequence chords |
Does this issue address sequence chords? e.g. |
Maybe I'm misunderstanding what @BrainSlugs83, @jvivs, and @sbrl are asking for, but I believe that functionality is already available via the |
@50Wliu Yep! That's what I'm after. In Visual Studio, they are called key chords I think. Is this issue for something different? I wonder if the documentation documents this. |
There's some discussion in atom/vim-mode#221 about allowing bindings based on multiple keys being smashed simultaneously. This is pretty tricky, because if we detected a
keydown
for a key involved in a chord, we'd need to wait for akeyup
before we could be sure the chord wasn't being triggered. Not a super high priority right now, but worth implementing in the future.The text was updated successfully, but these errors were encountered: