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

In vi-mode, the second input key will be eaten by the vi-mode. #1609

Open
sakurawald opened this issue Nov 18, 2024 · 1 comment
Open

In vi-mode, the second input key will be eaten by the vi-mode. #1609

sakurawald opened this issue Nov 18, 2024 · 1 comment
Labels

Comments

@sakurawald
Copy link
Contributor

sakurawald commented Nov 18, 2024

Given this typical configuration for vi-mode:

(define-key lem-vi-mode:*insert-keymap* "j k" 'lem-vi-mode/commands:vi-normal)

Try to input (create-object), you will get (create-objct) as result.
This is due to the character e is eaten by vi-mode.

In a real vim editor, if you define this key-sequence, and try to type j k.

  1. After you type in the j key, the vim will wait a timeout, and if there is no folloing keys, then the j is inserted.
  2. If you type in j and k as quickly as you can, then after the k is inputed, it will stop the waiting of next-key, and causing the character j and character k get inserted. (If there is no ambiguous key bindings).
@sakurawald
Copy link
Contributor Author

Similar issue is here: #1606
This is a problem related to the difference between vi-mode and the real vim editor.

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

No branches or pull requests

2 participants