On 2010-03-14, zaz wrote:
> Vim is a great editor! I like it and I use it.
>
> But now I have a complaint. Recently I set up a new Slackware Linux system
> and installed Gvim. When it starts up it reads in 28 *.vim files, including
> my .vimrc file, which is read in as number 10. (I determined this with
> :script). My .vimrc is read in as number 10, and apparently the subsequent
> 18 files override some specifications in my .vimrc. Right now it is almost
> unusable with special formating, comment handling, and it automatically
> doubles each '>' I enter.
>
> I can override this behavior with the command-line option "-u .vimrc", but
> then I loose features I like, such as spell-checking and other stuff. (Yes,
> I want to both eat and have my cake!) So it is going to be a research
> project to add back files like vimballPlugin, ftplugin.vim, etc. I don't
> know what they do, or what their dependencies are.
>
> My question is, how should one manage this complex installation, and how
> does one find out what plugins do, and what their dependencies are?
Vim loads a number of plugins when it starts, but they shouldn't be
doing anything so drastic as to make vim unusable for you. I'm
especially surprised that nine plugins are sourced before your
.vimrc. I think a good first step towards getting a handle on
what's going on would be to post the output of :scriptnames here so
that we can see exactly what's being loaded. You can copy and paste
the output, or you can save it to a file ("myscripts" in this
example) like this.
:set nomore
:redir > myscripts
:scriptnames
:redir END
:set more
Vim plugins don't normally change anything you've set in your .vimrc
unless you are editing particular file types in which case the
filetype plugin for that file type may make some special settings.
When you see odd behavior such as the doubling of >s, what kind of
file are you editing and what does
:verbose set filetype?
report?
The only way to really find out by yourself what plugins do is to
read them. An easier way is to report the specific problem
you're having here and let someone experienced with the associated
plugin give you a brief explanation. Dependencies vary among
plugins, so it would be difficult to give you a comprehensive
explanation here. For an overview, you can read
:help plugin
:help usr_43.txt
If any of this is not clear, just ask. I don't know yet how much
of an explanation you need.
Regards,
Gary
--
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
