-
Notifications
You must be signed in to change notification settings - Fork 7
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 Terminal Emulators <F2> Toggle Inserts Text #9
Comments
Hi, Can you tell me which version of vim you are running when the problem occurs and the contents of your .vimrc. In the meantime, You can also try removing lines 258 to 261 from the buffet.vim file, (if you are using the latest version from github.). At that position you will find a function. I have marked the lines to remove using ' > ' function! s:close() You can try removing the lines so that the above block becomes function! s:close() And thank you for notifying me of this error.. |
7.3.661 and 7.3.646 (MacVim) both show the error when launched from the command line. My .vimrc is here Removed the lines and saw no difference. Thanks for looking into this. |
Found some resources finally on this. I'd been using MacVim to avoid the issue, but recently started using vim in tmux. http://superuser.com/questions/258986/vim-strange-behaviour-f1-10 If I get it figured out I'll post back for anyone else that stumbles on this. |
In my .vimrc I have the following
When I hit F2 to toggle the buffer list, it shows the list just fine, but when I toggle out it ends up inserting some text.
It ends up adding a new line with Q
Before
Press
F2
twiceWhen I bind to other keys I get different results.
Bound to F5 it changes toggles case of words.
Before:
After:
One more time:
Now the weird part is that in MacVim with the GUI (I haven't checked gvim on Linux) it works perfectly... and if I run the same binary
/Applications/MacPorts/MacVim.app/Contents/MacOS/Vim
I get the weird behavior again.Oddly enough I use the same toggles for other plugins with no issues either.
Example:
works just fine.
The text was updated successfully, but these errors were encountered: