-
Notifications
You must be signed in to change notification settings - Fork 483
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
Bundle Exec Guard Command Not Working #748
Comments
If the prompt looks something like this:
Then it means guard is working (it's waiting for changes in files). Try changing an *.scss file and see if anything in the output changes. |
nope, the command prompt is the same as before I executed "bundle exec guard" Executing the command: H:\Uwamp\www\sunriserealty\sites\all\themes\sunrise_v1> |
ok, I tried starting from scratch. I deleted all gems. installed bundler (1.8.2), then ran 'bundle install" which completed - no errors. When I run 'bundle exec guard' i get the following error: H:\UwAmp\www\sunriserealty\sites\all\themes\sunrise_v1>bundle exec guard H:\UwAmp\www\sunriserealty\sites\all\themes\sunrise_v1> Not sure what it means and how to troubleshoot it. |
Contents of Gemfile: (Created by Drupal Omega 4 Subtheme): source 'https://rubygems.org' group :development do Sass, Compass and extensions.gem 'sass' # Sass. Guardgem 'guard' # Guard event handler. Dependency to prevent polling. Setup for multiple OS environments.Optionally remove the lines not specific to your OS.https://github.com/guard/guard#efficient-filesystem-handlinggem 'rb-inotify', '~> 0.9', :require => false # Linux end |
That's actually all I needed. I just fixed this and it should work in Guard version 2.12.3 (run If it still doesn't work, just paste the output like above (I don't use Windows, but years ago you could set the "window" width size in the command window preferences - which makes copying text from the console much easier). |
Thank you very much! Guard is now watching!!! I couldn't update guard to version 2.12.3, so to start fresh, I removed all gems, installed bundler and ran "bundle install". |
Thanks for taking the time to report the issue. Also, there's usually no reason to start fresh - most things can be fixed one way or another without doing drastic things. Did bundler complain about upgrading? What kind of error did you get? |
Not sure about the error. But the update did not go through. Have been trying to get my sass going for over 3 days with errors. It was just easier to remove gems and run bundle install to get them back. |
I have just installed ruby via ruby installer 1.9.3-p551 required for drupal omega 4 theming.
I have installed drush and it is working.
I installed bundle and ran bundle install for dependencies - all dependencies installed and met.
Yet when I use command:
"bundle exec guard"
nothing happens. I just get another command prompt. No errors either.
I tried running"drush omega-guard" with same results.
I tried running "bundle exec guard -d" same results, just another command prompt
I'm on a windows 7 machine.
ruby 1.9.3-p551 with devkit
using Pik for ruby management
Not sure what to do. Need help figuring this out.
The text was updated successfully, but these errors were encountered: