-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
E132: Function call depth is higher than 'maxfuncdepth' #45
Comments
Seconded, using Vundle. |
Same here, latest vim-airline on vim 7.3 huge. Some of the newer commits. On 3e1f8c8 everything fine! |
OK, the last commit, c0427e4, introduces the bug for me |
+1 - vundle, last commit. I just manually backed out of the commit to keep going. |
Same here since latest update. |
this is what happens when you commit and then go to sleep T_T. @sammcj, for some odd reason your |
i reproduced with the windows 7.3 install. it would appear that one of the 1000+ patches between 7.3 and 7.4 fixed this. |
@bling So, it is not the plugin's fault? |
@dalizard it is and it isn't. it just happens to be first error i've come across where the version of vim matters. i've already reverted the change since i know a lot of people like to use stock vim on whatever system they're on. but i'd like to leave this open so my initial change can make it in properly and support older versions. |
Yes it's fixed for me now. Thanks for the quick action (had the plugin disabled in the meanwhile). |
@bling Thank you. I am not using stock vim though. Installed via homebrew:
I hope this helps a bit :) |
yes, that definitely saved some time on my manual binary search :-). it turns out that 1058 is the version that fixes this. |
When launching vim:
my .vimrc:
Terminal is iTerm2 set to xterm-256colour
The text was updated successfully, but these errors were encountered: