18

My boot time for vim is about a half second (tested with "--startuptime"), but after I reload vimrc a couple times via source, it gets slower subsequently. I have not debugged .vimrc in a systematic way, so I am not sure how to proceed. Setting verbose helps to kind of see what is going on and I am almost certain that the .vimrc is being loaded more than once. (especially filetype.vim and ftplugin.vim) Whenever I press Ctrl-C to stop the hang, I get an error in filetype.vim, which I think is because vim spends most time trying to load filetype.vim. The most probable culprit I see is the auto reload of .vimrc:

if has("autocmd") autocmd bufwritepost .vimrc source $MYVIMRC "auto source vimrc endif

How could I stop this from happening?

Improve this question

2 Answers 2

Reset to default
28

The culprit here is your use of autocmd. When you define an auto-command with 

autocmd <Event> <Action>

vim defines a new auto command regardless of existing ones. So when you have several such auto commands in your .vimrc and repeatedly source it (in this case, for every write), you end up defining hundreds and thousands of auto commands which all do the same thing repeatedly. Very soon this will blow up and slow your vim session, which is what you've been noticing.

What you need to do instead, is to group your auto commands and then clear the definitions for that group with autocmd!. As a simple example:

augroup Group1 autocmd! autocmd <Event1> <Action1> autocmd <Event2> <Action2> ... augroup END

You can have as many groups as you like, which allows you to organize them by similar actions/events.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

2

This is my solution that also clears previous mappings:

augroup VimrcGroup autocmd! " Make changes effective after saving .vimrc. Beware that autocommands are " duplicated if .vimrc gets sourced again, unless they are wrapped in an " augroup and the autocommands are cleared first using 'autocmd!' autocmd bufwritepost $MYVIMRC call OnSavingVimrc() augroup END " Avoid infinite loops if !exists("*OnSavingVimrc") function! OnSavingVimrc() " Clear previous mappings, they don't go away automatically when sourcing vimrc mapclear echo "Sourcing Vimrc after saving it" source $MYVIMRC endfunction endif
Improve this answer

1 Comment

Should mapclear be mapclear | mapclear <buffer> | mapclear! | mapclear! <buffer> ?

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.