Closed codemoe closed 11 years ago
Yes, you're probably right. I've removed the offending #notify
method, so it shouldn't be trying to call non-existant methods. I've pushed a new version (1.1.0) to rubygems, so hopefully updating to that fixes the problem. Reopen this issue if it doesn't. Thanks.
I don't know if this is the right place for this but I was using Larvel-Guard with the respective guard gems and while I was working with the guard-sass gem, I noticed that the file wasn't processing itself into CSS and received the next ERROR
Guard::Sass failed to achieve its, exception was:
So after debuging a bit I found out that on line 164 of sass.rb it calls on guard.run_on_changes but that method is actually not defined anywhere so I found 2 possible solutions (I would like to know if I'm wrong or maybe it is an error)
guard.run_on_changes(paths) unless paths.empty?
[...] module ::Guard class Refresher < Guard def run_all
refresh
end end
[...]
Regards and I hope that someone can tell me if this is wrong or what happened (or even if I should put this on another place)