zhaocai
commented
11 years ago try something like this to start profiling.
profile start /var/log/vim/profile.log
profile func *
profile file *then open tagbar and do some regular activities. quit vim to see the profile results.
In my environment, tagbar and powerline seem working together well.
FUNCTIONS SORTED ON SELF TIME
count total (s) self (s) function
99 0.303654 0.295030 <SNR>234_AddScopedTags()
80 0.286208 0.242566 Powerline()
7 0.291156 0.194511 <SNR>124_get_action_table()
5 0.255596 0.174278 <SNR>234_HighlightTag()
650 0.147838 PythonFoldText()
1096 0.227809 0.129336 GetPythonFold()
2 0.099720 <SNR>135_uniq()
151 0.098473 GetBlockIndent()
2 0.087998 <SNR>64_guess()
2 0.068747 UltiSnips_FileTypeChanged()
1251 0.066067 <SNR>133__unify_path()
6 0.121848 0.051578 <SNR>133__scripts()
119 0.064420 0.048403 <SNR>234_ParseTagline()
1 0.077375 0.045305 <SNR>234_RenderKeepView()
2 0.230013 0.037300 194()
2614 0.029854 <SNR>147_convert2dictionary()
1 0.531913 0.026243 unite#util#smart_execute_command()
2 0.055374 0.025586 <SNR>147_convert2candidates()
14 0.027828 0.022728 neobundle#config#search()
186 0.042358 0.021102 <SNR>234_PrintTag()
Hi, thanks for this scheme. i just want to consult you for a solution about Powerline , but is not exactly about this scheme 's issue .
when i installed powerline and tagbar , i found vim become slow in buffer switching ,file loading . Meanwhile ,console window appeared temporarily in that time . so it would be nice for sharing your solution if you met with the same problem .