If I had to guess, I'd say that you may not have the feature compiled into Vim. Though, obviously, if omnicompletion works for other languages, I'm talking nonsense ;-)
Here's the output from ':version' on the machine I'm in front of now if you want to compare with yours. Mine's had both Perl and Vim compiled from source and I'm pretty certain I 'turned everything up to 11' with Vim.
:version
VIM - Vi IMproved 7.1 (2007 May 12, compiled May 14 2007 14:22:44)
MacOS X (unix) version
Compiled by johno@johns-g5.local
Huge version with Carbon GUI. Features included (+) or not (-):
+arabic +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +c
+indent -clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +cryptv -cscope +cursorshape +dialog_con_gui +
+diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi +file_in_path +find_in_path +folding -footer +fork() -gettext
+-hangul_input +iconv +insert_expand +jumplist +keymap +langmap
+libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +
+modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm
+mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme -netbean
+s_intg -osfiletype +path_extra +perl +postscript +printer +profile
+python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smarti
+ndent -sniff +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjec
+ts +title -toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writeb
+ackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/Applications/Vim.app/Contents/Resources/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MAC -fno-co
+mmon -fpascal-strings -Wall -Wno-unknown-pragmas -mdynamic-no-pic -pi
+p
e -I. -Iproto -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/Flat
+Carbon -g -O2 -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing
+
-I/usr/local/include -I/opt/local/include -I/usr/local/lib/perl5/5.8.
+8/darwin-thread-multi-2level/CORE -I/System/Library/Frameworks/Pytho
+n
.framework/Versions/2.3/include/python2.3 -I/usr/lib/ruby/1.8/powerpc
+-darwin8.0
Linking: gcc -L/usr/local/lib -o Vim -framework Carbon -lncurse
+s -liconv -L/usr/local/lib -L/opt/local/lib /usr/local/lib/perl5/5
+.
8.8/darwin-thread-multi-2level/auto/DynaLoader/DynaLoader.a -L/usr/loc
+al/lib/perl5/5.8.8/darwin-thread-multi-2level/CORE -lperl -lm -lc -fr
+a
mework Python -lruby -lobjc
Actually, I've just had grep through my shell history, and these're the configure options I used:
./configure --with-features=huge --enable-perlinterp --enable-pythonin
+terp --enable-rubyinterp --enable-multibyte
Hope that helps
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|