On Tue, 15 Jun 2010, aleCodd wrote:
>
> still after reinstalling all the vimruntime directory, the same
> problem exists.
>
> :(
Running the following gets everything set up minimally for me:
$ vim -u NONE -U NONE -N /tmp/test.js '+filetype plugin indent on' '+set
ft=javascript'
That is:
do^X^O completes to 'document.'
document.^X^O completes to a list starting with 'anchors'
Running ':scriptnames' produces:
1: /usr/share/vim/vim72/filetype.vim
[...trimming known-irrelevant ftdetect files...]
9: /usr/share/vim/vim72/ftplugin.vim
10: /usr/share/vim/vim72/indent.vim
11: /usr/share/vim/vim72/ftplugin/javascript.vim
12: /usr/share/vim/vim72/indent/javascript.vim
13: /usr/share/vim/vim72/autoload/javascriptcomplete.vim
Maybe you're picking up the wrong version of something in that list?
Maybe the portion I've trimmed contains some broken filetype detection?
Maybe you've overridden javascript.vim or javascriptcomplete.vim in your home
directory?
Most filetype plugins have boilerplate similar to:
===========================
if exists('b:did_ftplugin')
finish
endif
let b:did_ftplugin = 1
" [...etc...]
===========================
...which prevents a second filetype plugin from running.
--
Best,
Ben
--
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
