-
Notifications
You must be signed in to change notification settings - Fork 18
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
vim-over gets invoked in insert-mode #34
Comments
Thanks for issues. |
As in the examples: Start Also, if you then exit to normal mode, and press |
I'm loading vim-over with pathogen, no settings in vim-over has been altered.
|
So, the insertion of I assume this is caused by |
Thanks :) |
Hm, okay. The problem is lesser, meaning less text is inserted – now I figured out part the problem -- and somewhere in my vimrc, I call However, this is still a bug – if you exit, then enter insert-mode in the command line window, you'll get the same results. How to reproduce: In normal-mode press |
hmmm....but I can't reproduce :( |
Can't reproduce either. |
This can probably be closed. Vim-over works perfect on my current vim-setup, and has been for years. May have been some conflict with the specific vim-version I was running at that time. |
It seems vim-over starts matching in insert-mode. This can get really annoying when writing plaintext documents. Every time a word ends with an 's', and is followed by a comma, vim starts matching the following word. When this happens, certain key combinations will also start acting weird, inserting text like
<Plug>(over-cmdline-something)
in the buffer.The text was updated successfully, but these errors were encountered: