Doesn't work on Vim even after compiling

[mbackermann]

I'm trying to use it with Vim 8.1, which uses ruby 2.5.1.

I followed the installation instructions, ran ruby extconf.rb and got the following output checking for float.h... yes checking for ruby.h... yes checking for stdlib.h... yes checking for string.h... yes checking for fcntl.h... yes checking for stdint.h... yes checking for sys/errno.h... yes checking for sys/socket.h... yes checking for ruby/st.h... yes checking for st.h... yes checking for pthread_create() in -lpthread... yes creating Makefile

then I ran make and got:

compiling ext.c compiling heap.c compiling match.c compiling matcher.c compiling watchman.c linking shared-object ext.bundle

but when I try to access it inside vim, I got the following message

command-t.vim could not load the C extension. Please see INSTALLATION and TROUBLE-SHOOTING in the help. Vim Ruby version: 2.5.1-p57 For more information type: :help command-t

My ruby version is 2.5.1. I also tried compiling it with ruby 2.5.0 and I got a different message, telling me that the Command-T version was wrong. But when I compile it with ruby 2.5.1 I got the message that it's not compiled at all.

[wincent]

What's the output of ruby --version and vim --version on the command line? What operating system and version are you on?

[mbackermann]

mac OS High Sierra (10.13.6) ruby --version ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]

vim --version VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 22 2018 05:24:30) macOS version Included patches: 1-202 Compiled by Homebrew Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_sgr -tag_any_white +arabic +file_in_path -mouse_sysmouse -tcl +autocmd +find_in_path +mouse_urxvt +termguicolors -autoservername +float +mouse_xterm +terminal -balloon_eval +folding +multi_byte +terminfo +balloon_eval_term -footer +multi_lang +termresponse -browse +fork() -mzscheme +textobjects ++builtin_terms -gettext +netbeans_intg +timers +byte_offset -hangul_input +num64 +title +channel +iconv +packages -toolbar +cindent +insert_expand +path_extra +user_commands -clientserver +job +perl +vartabs +clipboard +jumplist +persistent_undo +vertsplit +cmdline_compl +keymap +postscript +virtualedit +cmdline_hist +lambda +printer +visual +cmdline_info +langmap +profile +visualextra +comments +libcall -python +viminfo +conceal +linebreak +python3 +vreplace +cryptv +lispindent +quickfix +wildignore +cscope +listcmds +reltime +wildmenu +cursorbind +localmap +rightleft +windows +cursorshape -lua +ruby +writebackup +dialog_con +menu +scrollbind -X11 +diff +mksession +signs -xfontset +digraphs +modify_fname +smartindent -xim -dnd +mouse +startuptime -xpm -ebcdic -mouseshape +statusline -xsmp +emacs_tags +mouse_dec -sun_workshop -xterm_clipboard +eval -mouse_gpm +syntax -xterm_save +ex_extra -mouse_jsbterm +tag_binary +extra_search +mouse_netterm +tag_old_static system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" defaults file: "$VIMRUNTIME/defaults.vim" fall-back for $VIM: "/usr/local/share/vim" Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X -DMACOS_X_DARWIN -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: clang -L. -fstack-protector -L/usr/local/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/readline/lib -L/usr/local/lib -o vim -lncurses -liconv -framework AppKit -mmacosx-version-min=10.13 -fstack-protector-strong -L/usr/local/lib -L/usr/local/Cellar/perl/5.28.0/lib/perl5/5.28.0/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -L/usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/lib/python3.7/config-3.7m-darwin -lpython3.7m -framework CoreFoundation -lruby.2.5.1 -lobjc

[wincent]

Nothing looks out of order there. Personally I'd try a cleaning (make clean) and rebuilding to see if the problem goes away. Failing that, I think I'd change this line to:

raise

to see whether I could see more detail about the exception that is probably being raised when you're trying to use Command-T. Even if you do that, there is a chance that the error text might get swallowed or overwritten when Vim updates the UI, so it might be necessary to log it to a file so you can actually see it.

[mbackermann]

Actually, I could solve using rvm use system. Probably was a problem with RVM. It's now working. Thanks a lot all the help.