Run `brew linkapps macvim` to symlink these to /Applications. usr/local/Cellar/macvim/7.4-85 (1910 files, 35M)īuilt from source with: -with-lua -with-luajit -with-python3 -with-override-system-vim Here's the current info: $ brew info macvim I want the most recent version only to be my default vim everywhere, ie, when I type gvim or vim from the command line.īrew linkapps macvim does not work, ie, gvim still gives "No such file" after running it. JSON, and I've checked it compiles with 1.8.I have 4 versions of macvim installed in homebrew's Cellar folder. Next branch ( ) if you'd like to try this out it no longer depends on Think before it compiles correctly on older versions of The JSON dependency, but it will need a bit more work I I have a commit on the next branch that removes Ruby/command-t/scanner/file_scanner/watchman_file_scanner.rbĪnd seeing if that works. I have a suspicion that Ruby is failing to load the JSONĭoesn't distinguish between that and failure to load o Vim -framework Cocoa -framework Carbon -lncurses -liconv -framework Cocoa -fstack-protector -L/usr/local/lib -L/System/Library/Perl/5.12/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -framework Python -framework Ruby Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -no-cpp-precomp -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 +extra_search -mouse_jsbterm -sun_workshop -xpmįall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"Ĭompilation: clang -c -I. +ex_extra -mouse_gpm +statusline -xterm_save +eval +mouse_dec +startuptime -xterm_clipboard +cursorshape +localmap +reltime +wildmenu +cursorbind +listcmds +quickfix +wildignore +cmdline_info +keymap +postscript +virtualedit +cmdline_hist +jumplist +persistent_undo +vertsplit +cmdline_compl +insert_expand +perl +user_commands +clipboard +iconv +path_extra +transparency +clientserver -hangul_input +odbeditor +toolbar +byte_offset +fullscreen -mzscheme +textobjects ++builtin_terms +fork() +multi_lang +termresponse +autocmd +float +mouse_urxvt -tag_any_white +arabic +find_in_path -mouse_sysmouse +tag_old_static +acl +file_in_path +mouse_sgr +tag_binary $ otool -L /usr/local/Cellar/macvim/7.4-72/MacVim.app/Contents/MacOS/Vim | grep ruby System/Library/Frameworks/amework/Versions/1.8/usr/lib/libruby.1.dylib (compatibility version 1.8.0, current version 1.8.7) arch i386 -arch x86_64 -lruby -lpthread -ldl -lobjcĪpple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) L/System/Library/Frameworks/amework/Versions/1.8/usr/lib -L. D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -fno-common -arch i386 -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common -std=c99 -Wall -Wextra -Wno-unused-parameter -c matcher.cĬc -arch i386 -arch x86_64 -pipe -bundle -undefined dynamic_lookup -o ext.bundle ext.o match.o matcher.o -L. I/System/Library/Frameworks/amework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin12.0 -I/System/Library/Frameworks/amework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin12.0 -I. D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -fno-common -arch i386 -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common -std=c99 -Wall -Wextra -Wno-unused-parameter -c match.cĬlang -I. D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -fno-common -arch i386 -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE -fno-common -pipe -fno-common -std=c99 -Wall -Wextra -Wno-unused-parameter -c ext.cĬlang -I. $ cd ~/.vim/bundle/Command-T/ruby/command-tĬlang -I. Me to how to get more debug info of why the extension isn't Here's everything, I'm hoping you have an idea or can point The build also completed fine but likewise in Vim it doesn't My MacVimīuilds (I've tried both a distributed binary and a Homebrewīuild) indicate clang compilation, so I setĬC=clang as you can see below. Is running Mountain Lion, and by default part of theĮxtension build appears to use gcc. I'm pretty sure I'm not flubbing the Ruby version here, The extension build runs just fine, but I get the message in I'm sure these install issues are a huge thorn in your side,īut I've never had trouble with past versions and I'm miffed Thanks for Command-T, it's served me well for a long timeĪnd I was looking forward to the pthreads update since it'sĪpparently been awhile since I updated my plugin version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |