DHAVE_RUBY_H -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -fno-common -g -O2 -pipe -fno-common -std=c99 -Wall -Wextra -Wno-unused-parameter -c ext.c L/usr/local/lib -o vim -lm -lncurses -lruby-static -lobjc Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon -g -O2 -D_FORTIFY_SOURCE=1 -I/usr/local/lib/ruby/1.8/i686-darwin10.4.0 -DRUBY_VERSION=18 X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_saveįall-back for $VIM: "/usr/local/share/vim"Ĭompilation: gcc -c -I. +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +printer -profile -python +quickfix +reltime -rightleft +ruby +scrollbind +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra -perl +postscript mouse_jsbterm -mouse_netterm -mouse_sysmouse +mouse_xterm -multi_byte +menu +mksession +modify_fname +mouse -mouseshape -mouse_dec -mouse_gpm +jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap +float +folding -footer +fork() -gettext -hangul_input -iconv +insert_expand emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +cryptv -cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent VIM - Vi IMproved 7.2 (2008 Aug 9, compiled 19:05:14)Ĭompiled by version without GUI. With "command-t.vim could not load the C extension" Vim ruby runner install#I have the exact same problem as the original poster.Įverything seems to install fine, but t fails "command-t.vim could not load the C extension" when If you’ve made some changes to your development database and want them to exist in your test database before running the specs, just run rake db:test:prepare once and you’re good to go.After a seemingly successful install, I get the error The first time you click in an error line in Firefox, it will prompt you to confirm that you want to use open_vim as the program to open vim:// links. Now give it execution permition by running chmod +x ~/.vim/bin/open_vim. This solution was tested using VIM 7.2 in a Ubuntu 8.04 box.Ĭreate a new file with the following content and put it in ~/.vim/bin/run_rspec.rb Take a look at the VIM Makefile and serch for something like enable ruby-interp. If all you have is “-ruby” you’ll need to re-compile VIM with this option enabled. To see if your VIM has the Ruby support, run :version and search for “+ruby”. For this solution to work your VIM must have been compiled with the +ruby option, which enables a Ruby interface for VIM. The solution was to adapt the Gedit script, put it in an external Ruby file and create a new function to execute this script in my. If you forget what was the error message or the failing spec, you will need to re-run the whole thing, since the output shown by VIM was temporary. Another thing that I dislike is that VIM will put all specs execution output in a temporary view mode and wait until you press or run another command, going back immediately to the spec buffer. The downside is that all the test database is reloaded, making the tests unnecessarily slow. In rails.vim, when we have an open Rspec file and run :Rake this file is executed with Rspec. Since I moved back to VIM recently, I wanted to do the same using the rails.vim plugin. Vim ruby runner code#This page shows even the code fragments for the failing specs, which is very useful for solving problems. Another thing that I like in the script is that it uses the Rspec HTML output, generating an HTML page which is shown in a new Firefox tab. This makes the tests much faster, in special if all we want is to run the specs of a single Rspec file. It was very useful to me since the script already includes all the necessary rspec dependencies in the load path and executes the declared specs wtihout running the dbtest:prepare Rake task. In Gedit I was always using this script to execute the current Rspec file, when developing Rails apps.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |