-
Notifications
You must be signed in to change notification settings - Fork 199
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
Merge Vim emulation rewrite. #442
Conversation
Michał J Gajda wrote:
I couldn't reproduce that error about unhandled event, could you post a test?
These are bugs, I'll fix them.
Vim2 is intended as a complete replacement for Vim module. I think we should make a release with both implementations, receive some more feedback and then in some future release remove the old one. As for the compatibility layer, I think it's not worth the effort.
It's hard to tell, because current Vim emulation doesn't have any tests.
Sure, take as long as you need. Thank you for review. |
Something like:
For a problem with the block insertion at the end of file:
I can no longer reproduce "event" bug in the current version. |
After entering Ex mode with ':' trying to quit it with just leads to: |
Two more things I spotted that would be good to fix before merging:
|
I've never used tag operations in yi, how do I test them? |
Dear Dmitry, In visual and insert keymaps: Underlying ops on a tag stack (pushTagStack, popTagStack, and Reading "tags" file is implemented separately in Yi.Tags.Best |
Seems to work for me. I would open issues for TagStack and isearch history and finalize merging, unless anybody is against. |
You can try it out by launching
yi --as=vim2
and configure it using yi/example-configs/yi-vim2.hs as a starting point.Tests can be run with
cabal test
, please read yi/src/tests/vimtests/README.rst for some documentation.Let's use this pull request as a beta release discussion of vim2. When we agree that it's not horribly broken in some way, we can merge it and call it yi-0.7.0