Re: How to debug when vim becomes quite slow?

Excerpts from kindle4ever's message of Sat Feb 18 15:15:00 +0100 2012:
> When i open a file with 4000line code, the response of vim becomes quit
> slow. At the mean time i input a word, vim costs 40% cpu. After switching
> to another vimrc, it works fine again.
wild guess:
- switch of syntax : syn off
- switch off folding: set fdm=manual

get ideas from "LargeFile" plugin on www.vim.org

You already have a working and a bad .vimrc?

but first of all: Learn how to track down errors. You do so by
a) finding a case which works
b) compraing the case which does not by the one which does step by step.

in your case I'd start with empty .vimrc. If it does goto the middle of
your .vimrc and add a "finish".
bad? continue putting the first half into two pieces by adding finish
good? remove "finish" and put the second half of the .vimrc into pieces.

Vim ignores everything after "finish"

This technic is called bisecting.

Then you'll find the cause fast.

If you find that line causing the trouble is "plugin on" then move
plugin/*.vim files somewhere else (temporarely) or use vim-addon-manager
which is particularly good at starting vim with different plugin
combinations easily.

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