Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I love the omega-guard drush implementation.
However, I can't start it, due to the following error
ERROR: guard start was called with arguments ["--no-color"]
If I remove the --no-color from the omega.drush.inc file in the following line. It's ok.
$command = 'bundle exec guard --no-color --no-interactions';
Is it a valid argument? Or do I miss something on my system?
Comment | File | Size | Author |
---|---|---|---|
#9 | 2008896-9-omega-guard-no-color.patch | 488 bytes | joelpittet |
Comments
Comment #1
dddbbb CreditAttribution: dddbbb commentedI'm also experiencing this issue.
Comment #2
fubhy CreditAttribution: fubhy commentedWill look into it on Monday. Note: You can also navigate into the subtheme folder and use "bundle exec guard" to achieve (nearly) the same effect.
Comment #3
segovia94 CreditAttribution: segovia94 commentedI have the same issue. In addition, when trying to do "bundle exec guard", it starts but then throws an error.
c:/Ruby193/lib/ruby/gems/1.9.1/gems/listen-1.0.3/lib/listen/adapter.rb:195:in `require': cannot load such file -- wdm (LoadError)
Comment #4
fubhy CreditAttribution: fubhy commentedThat's a problem with your setup. You are missing a dependency (wdm). Fix: "gem install wdm" (looks like you are on Windows, right?). Not sure why it requires wdm, I thought it works without that. But oh well, if it needs it, just install it.
Comment #5
segovia94 CreditAttribution: segovia94 commentedYep, Windows 7. That's the funny thing. wdm is installed already.
I came across this post which fixed the wdm issue for me.
http://stackoverflow.com/questions/16232960/guard-wont-load-wdm
So using the suggestion there allows "bundle exec guard" to work. However "drush omega-guard" still throws the "--no-color" error.
Comment #6
jdflorez CreditAttribution: jdflorez commentedOne question Segovia, what does the file .ruby-version (thats in your theme folder) say?
Comment #7
segovia94 CreditAttribution: segovia94 commentedThe ruby version is 1.9.3. Originally I was on 1.9.1, but I uninstalled it thinking that perhaps I had something installed incorrectly. However, 1.9.3 gave the same results.
Comment #8
Adam S CreditAttribution: Adam S commentedI had a similiar problem on Windows 7. I'll post it here because it probably has the same cause as this and will show in Google and issue queue searches.
on windows at C;\wamp\www\MYSITE\sites\all\themes\MYOMEGASUBTHEME compass watch is typed in. The response is
After some fidgeting trying to uninstall and reinstall Sass, Compass, and Susy, I tried
gem install toolkit
. When I typecompass watch
things work like they should.Comment #9
joelpittetRemoving the --no-color flag seems to fix the issue. Here's a patch.
Comment #10
tancConfirmed #9. Removing --no-color allows guard to run fine.
Comment #11
fubhy CreditAttribution: fubhy commentedI put the --no-color there for a reason (because otherwise the output can't be parsed properly). This is not a solution. Will take a look and see how we can integrate the guard console better with drush. Again, as a temporary solution you can just invoke "bundle exec guard" manually, although that requires you to navigate into the theme folder.
Comment #12
fubhy CreditAttribution: fubhy commentedCommited to 4.x-dev with some slight modifications. Thanks