-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zsh:1: command not found: spec #12
Comments
Please try to make sure spec is in your path. try: ~➤ which spec ~/myproject ✗ ➤ which spec ruby-1.8.7-p249@x3 |
I get |
If you are outside of vim and you run spec and that doesn't work, then this plugin can't magically make it work :) Is that what i'm hearing? Try to do a gem install rspec --version 1.3.0 |
To clarify, you must be able to run
from your command line. if that works, and vim doesn't work, then we have some path problem between the command line and vim. if however that line doesn't work, then you have a system problem of not locating the spec binary, which is outside the scope of this plugin |
im using rspec 2, is possible to use this plugin with rspec2? when i tried to install rspec 1.3.0 i recieve errors
when i run
I tried install rspec 1.3.0 but this not solving the problem. gem list
I aliased spec='rspec' in zshrc but this not solve the problem too :P |
I myself don't use the plugin for rspec2 so I haven't had time to make sure it works 100%. I have heard that it does from another contributor. It should theoretically find the 'rspec' command if it's in your path. Can you do |
I can confirm with ruby 1.9.3, rspec-2.8.0 that it does find the (correct) path on the cli but not with this plugin. I can as well do
|
You should use https://github.com/tpope/vim-rvm for better rvm support within gvim. If you start your gvim from the terminal after cd-ing into your desired directory, things will be fine, otherwise, you should use tpope's rvm and call :Rvm to switch to the correct context as per your .rvmrc before you execute your tests. |
When I try to run RunSpecs i receive this error.
The text was updated successfully, but these errors were encountered: