Thread: Using a custom _vimrc with Cream
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: William M. <wi...@kn...> - 2003-03-31 14:07:07
|
Hi all, I'm still getting familiar with Cream and have been sourcing the _vimrc file directly since Cream was not autoloading. I am using Cream under WinNT and used the Windows installer. It turns out that my custom _vimrc in my $HOME directory is getting called instead of the $VIM/_vimrc file (according to Vim's helpfile, only the first init file gets called--read ':help VIMINIT' for details). So, I added a source $VIM/cream/_vimrc to the beginning of my personal _vimrc which caused Cream to load but creates strange results with the toolbar (no icons). Simply doing a :source $VIM/cream/_vimrc clears things up. It's curious that sourcing this file from script causes the problem but there is no problem when calling it after Vim has started. I also tried putting the source command at the end of my _vimrc but got the same results. Renaming my _vimrc so that the $VIM/_vimrc file loads instead of my custom version produces the same results. Has anyone experienced this behavior? Any suggestions besides resourcing the $VIM/_vimrc? Reading the FAQ, I noticed a section that mentioned putting personal customizations into a cream-user.vim file. Is this where all my current settings in $HOME/_vimrc should go? Seems like the FAQ should mention potential problems with custom _vimrc files not starting Cream. Something under Advanced Vim Users like the following would be helpful: Q: I see no changes after installing Cream. A: If you have a custom _vimrc in your home directory that is being loaded, the $VIM/_vimrc file which Cream installed will not be used. You can add the following line to the beginning of your custom _vimrc to load Cream: source $VIM/cream/_vimrc Thanks, William -- Knowmad Services Inc. http://www.knowmad.com |