-
Notifications
You must be signed in to change notification settings - Fork 283
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
Unable to create mappings with colon. #2883
Comments
Thanks for logging the issue, @jordwalke ! There's a gap in our input handling code right now - it's only handling direct key productions (so our input code sees Various keys that require shift pressed that would be expected to bind correctly like @zbaylin set up the framework in #2687 for us to handle this correctly - I need to get it hooked up. |
Fixes #2883 __TODO:__ - [x] Make use of our new keyboard layout module (thanks @zbaylin !) - [x] Bring back special-key handling - [x] Add test case for #2883 - [x] Fix scancodes / verify 'AllKeysReleased' behavior for Control+Tab - [x] Fix bug with C-C / C-D / C-U being forwarded to Vim - [x] Fix newly introduced bug with Control+Shift+P/Cmd+Shift+P __Next steps:__ - #2114 - respect 'no recursive' flag for remaps (#2908) - #2293 - Update the `keyDown` function in `EditorInput` to take a list of candidates as opposed to a single keypress. - #2293 - Enable some bindings that were previously blocked: - `<C-W>+` - `<C-W>_` - `<C-W>|` - Refactor input event subscription and `Sld2.TextInput.start` out of store and into a `Service_Input` sub - Move `input` utility to common integration test infrastructure - Remove the `KeyboardInput` Action
Some regressions have been identified with #2902, so I'll back it out and work through bringing it back in |
Actually - tracking those issues separately in #2916 - fix still in 😄 |
__Issue:__ All of our bindings, whether defined by `nmap` or `nnoremap`, were allowing recursive definitions. This breaks the case in #2114, where the remaps would bounce back and forth until they hit our recursion limit. __Defect:__ We weren't gating recursive remaps, aside from the recursion limit. __Fix:__ Define and handle no-recursive remaps correctly. __Todo:__ - [x] Update existing test cases to pick up new API - [x] Add test cases to validate non-recursive maps - [x] Get tests green - [x] Add integration test covering #2114 - [x] Update CHANGES - [x] Rebase on #2883 when merged Fixes #2114 Depends on #2883 Related #1551
Looks like the latest release fixes this. Also fixed my other mapping |
Awesome - thanks @jordwalke for confirming! (and thanks @zbaylin for all the work setting up auto-update 😄 ) |
I opened the command prompt to create mappings and it would not accept mappings that involved
:
.(I map
;
to:
in normal mode to save myself the shift key).I think there may be issues with other kinds of mappings, but I can't recall which exact ones failed. I'll reply here with more info if I come across those again.
The text was updated successfully, but these errors were encountered: