> > E121: Undefined variable: g:vundle_last_status > > E15: Invalid expression: 'error' == g:vundle_last_status > > These might be the result of another error, causing the variables not > being set.
I've never had any problems before patch 260. since there was a discussion going on that patch, I reported those error as I think my (very) little knowledge of vimscript isn't enough to debug this problem. I might give it a try if I find some spare time, but in the meanwhile I thought that reporting those errors could still be useful > > the following looks more like it's the script author fault, but I'm not > > sure if all the errors are due to the illegal function name or not, so I'm > > pasting them all: > > > Clearly these function names starting with "vdebug:" are illegal. yep, but as I said I wasn't sure if all the following errors were due to that or there was some other change/side effect I wan't aware of. > Did Jon Cairns write this? Perhaps you can contact him. I'll open an issue on github -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
