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

No command accepts characters in a keybinding #1079

Open
Saevon opened this issue Aug 24, 2016 · 0 comments
Open

No command accepts characters in a keybinding #1079

Saevon opened this issue Aug 24, 2016 · 0 comments

Comments

@Saevon
Copy link

Saevon commented Aug 24, 2016

Any keybindings with characters in them (e.g. : to go to Ex Mode) take priority over vim commands. Specifically for commands that take a character as input

r: opens the Ex Mode rather than replacing the current character with a colon
t: does the same rather than jumping to the next :

The commands remain in their unfinished state as well, capturing the next character you press.

If you create a sublime keybinding which consists of just characters !! or ? these also take priority.

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

1 participant