Using guard live reload and guard compass seems to conflict -


i'm trying use guard livereload , guard compass together. here file

a sample guardfile

    # more info @ https://github.com/guard/guard#readme      guard 'compass'       watch('^sass/(.*)\.s[ac]ss')     end      guard 'livereload'       watch(%r{.+\.(css|html|js)$})     end      # concatenate javascript files specified in :files public/js/all.js     #guard :concat, type: "js", files: %w(), input_dir: "public/js", output: "public/js/all"      #guard :concat, type: "css", files: %w(), input_dir: "public/css", output: "public/css/all"      #guard 'uglify', :destination_file => "public/javascripts/application.js"     #  watch (%r{app/assets/javascripts/application.js})     #end 

when begin guard, without enabling chrome live reload extension, sass files compiled , work well.

but when enable livereload extension, terminal says browser connected, , when make changes in sass files, nothing happens (neither page reloads, nor sass files compiled).

does have ideas ?

for moment, i'm lauching 2 terminals in windows, 1 compass watch, , 1 guard (i commented compass part of guardfile).

if has better solution


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -