Closed kennethlove closed 14 years ago
Hi, thanks for the report. What version of the plugin are you using, and on which platform? Can you paste the output of running vim --version?
MacVim. Plugin version is 2.3.0.
Output below:
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Nov 16 2009 12:35:13)
MacOS X (unix) version
Included patches: 1-284
Compiled by kennethlove@kenneth-loves-macbook-pro.local
Huge version with MacVim GUI. Features included (+) or not (-):
+arabic +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
+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
+float +folding -footer +fork() +fullscreen -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_sysmouse
+mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg +odbeditor
-osfiletype +path_extra +perl +postscript +printer +profile +python +quickfix
+reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline
-sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo
+termresponse +textobjects +title +toolbar +transparency +user_commands
+vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore
+wildmenu +windows +writebackup -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/MacVim.app/Contents/Resources/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O -arch i386 -D_FORTIFY_SOURCE=1 -g -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -I/usr/local/include -I/System/Library/Perl/5.8.8/darwin-thread-multi-2level/CORE -I/usr/local/include/python2.6
Linking: gcc -L. -arch i386 -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon -lncurses -liconv -L/usr/local/lib /System/Library/Perl/5.8.8/darwin-thread-multi-2level/auto/DynaLoader/DynaLoader.a -L/System/Library/Perl/5.8.8/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -framework Python -framework Ruby
Hmm, I can't reproduce on any version of MacVim 7.2 against ruby 1.8.7. What version of Ruby are you using?
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.2.0]
I have fuzzyfinder and fuzzyfinder_textmate installed as well and I noticed a warning about them at macvim startup. Could that be related?
Darn. Does a previous version of the plugin work for you?
re: fuzzyfinder_textmate, yes. Try renaming that to zzfuzzyfinder_textmate.vim so that it's last in the load order and see if that helps...
moving fuzzyfinder_textmate seems to fix it. maybe you should warn about that in the docs? thanks for troubleshooting.
Great. I'll make the warning message from detecting fuzzyfinder_textmate more explicit about how to work around it.
I get this error every time I try to invoke LustyExplorer:
Error detected while processing function50_LustyFilesystemExplorerFromHereStart:
line 1:
NameError: (eval):31: uninitialized constant Lusty
Sometimes it's without the "FromHere", obviously (when not using lr)