Re: Profiling vim

vim -V20/tmp/log will write a logfile.

use tail -f (on *nix like os) to follow the file.
If it goes crazy you have chance to understand what is going on.

Also try to find out whether it happen in insert or normal mode or
command mode (eg after typing :)

Yes - bisecting is a good way - and bisecting plugins is easy.
vim-addon-manager even automates it.

Think about which plugins could have async behaviour - eg which
utilize CPU every X seconds - maybe you can limit the numeber of plugins
which are more likely to cause it fast.

If you paste your plugin list, maybe the list can also help judging 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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.