Saturday, April 14, 2012

Re: How can I find which VIM plugin guilty for overloading my CPU

I'll try this approach. Thank you, guys!
vineri, 13 aprilie 2012, 13:37:51 UTC+3, MarcWeber a scris:
> first try to reproduce the bug. This usually is hard. You must be
> confident that you found the "cause" - that's why you have to work on
> reproducing it.
>
> way 1)
> Remove plugins piecewise and retry. VAM is particular useful to do so.
>
> way 2)
> use vim -V20/tmp/log and see which plugins does much work (assuming its
> viml causing the work and not python,ruby or a system command)
>
> way 3)
> assume its a vim bug, try to find out what is causing it by switching
> off syntax, folding (whatever comes to your mind)
> test vim vs gvim. Try older vim to find out whether its a new bug. Try
> different operating system ..
>
> Those ideas should help you getting started with debugging it.
>
> Marc Weber

--
You received this message from the "vim_use" 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

No comments: