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

Sass --watch doesn't find anything, not compiling #719

Closed
alexmngn opened this Issue Apr 22, 2013 · 39 comments

Comments

Projects
None yet
@alexmngn

alexmngn commented Apr 22, 2013

I'm trying to use SASS but I got some issue with it, is not compiling anything. I tried different things to troubleshoot, is still not working.

Ruby 1.8.7
Sass 3.2.7
Mac OS X 10.8.3

What I try:

Install Ruby 2.0.0
Uninstall Sass
Reinstall Sass
Install the gem "listen"
Since I installed the gem "listen", I got this issue when I'm using the command sass --watch myfolder

>>> Sass is watching for changes. Press Ctrl-C to stop.
[Listen warning]:
Listen::MultiListener is deprecated, please use Listen::Listener instead.

Any idea?

Thanks.
Alexis.

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 Apr 22, 2013

Contributor

What is the contents of myfolder?

Contributor

nex3 commented Apr 22, 2013

What is the contents of myfolder?

@alexmngn

This comment has been minimized.

Show comment
Hide comment
@alexmngn

alexmngn Apr 23, 2013

Just a *.scss file.

alexmngn commented Apr 23, 2013

Just a *.scss file.

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 Apr 23, 2013

Contributor

Sass compiles .sass files to .css. It won't do anything to plain .css files.

Contributor

nex3 commented Apr 23, 2013

Sass compiles .sass files to .css. It won't do anything to plain .css files.

@alexmngn

This comment has been minimized.

Show comment
Hide comment
@alexmngn

alexmngn commented Apr 23, 2013

Edited.

@ahmedelgabri

This comment has been minimized.

Show comment
Hide comment
@ahmedelgabri

ahmedelgabri Apr 23, 2013

having the same issue

sass --watch css/scss/main.scss:css/main.css                                                  
>>> Sass is watching for changes. Press Ctrl-C to stop.
[Listen warning]:
Listen::MultiListener is deprecated, please use Listen::Listener instead.

ahmedelgabri commented Apr 23, 2013

having the same issue

sass --watch css/scss/main.scss:css/main.css                                                  
>>> Sass is watching for changes. Press Ctrl-C to stop.
[Listen warning]:
Listen::MultiListener is deprecated, please use Listen::Listener instead.
@athaeryn

This comment has been minimized.

Show comment
Hide comment
@athaeryn

athaeryn Apr 24, 2013

Same issue. I think the problem was listen-1.0.2. I was having the problem on my work computer but not my personal one. My personal one had listen (0.7.3) while my work one had listen (1.0.2, 0.7.3). Removing 1.0.2 got things working on my work computer again.

athaeryn commented Apr 24, 2013

Same issue. I think the problem was listen-1.0.2. I was having the problem on my work computer but not my personal one. My personal one had listen (0.7.3) while my work one had listen (1.0.2, 0.7.3). Removing 1.0.2 got things working on my work computer again.

@athaeryn

This comment has been minimized.

Show comment
Hide comment
@athaeryn

athaeryn Apr 24, 2013

Could this be as simple as changing MultiListener to Listener on line 266 of sass/lib/sass/plugin/compiler.rb?

athaeryn commented Apr 24, 2013

Could this be as simple as changing MultiListener to Listener on line 266 of sass/lib/sass/plugin/compiler.rb?

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 Apr 24, 2013

Contributor

Could this be as simple as changing MultiListener to Listener on line 266 of sass/lib/sass/plugin/compiler.rb?

Can someone try this and report whether it works?

Contributor

nex3 commented Apr 24, 2013

Could this be as simple as changing MultiListener to Listener on line 266 of sass/lib/sass/plugin/compiler.rb?

Can someone try this and report whether it works?

@athaeryn

This comment has been minimized.

Show comment
Hide comment
@athaeryn

athaeryn Apr 24, 2013

I'm trying it but having some trouble building the gem...

Just swapping it out and running rake passes all tests though.

I could be doing something wrong though, I'm not super familiar with serious gem development...

athaeryn commented Apr 24, 2013

I'm trying it but having some trouble building the gem...

Just swapping it out and running rake passes all tests though.

I could be doing something wrong though, I'm not super familiar with serious gem development...

athaeryn added a commit to athaeryn/sass that referenced this issue Apr 25, 2013

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol Apr 29, 2013

@athaeryn, your fork breaks the --sourcemap option.

mgol commented Apr 29, 2013

@athaeryn, your fork breaks the --sourcemap option.

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol Apr 29, 2013

I've tried changing MultiListener to Listener and the warning disappears but watch still doesn't fire. My output:

$ sass --compass --sourcemap --watch . 
>>> Sass is watching for changes. Press Ctrl-C to stop.
  overwrite ./styles/print.css
  overwrite ./styles/print.css.map
WARNING: Couldn't determine public URL for "sprite/*.png" while generating sourcemap.
  Without a public URL, there's nothing for the source map to link to.
  Custom importers should define the #public_url method.

  overwrite ./styles/screen.css
  overwrite ./styles/screen.css.map
$ 

It just compiles once and that's all... Updating the listen submodule to 1.0.3 after making this change doesn't help either.

mgol commented Apr 29, 2013

I've tried changing MultiListener to Listener and the warning disappears but watch still doesn't fire. My output:

$ sass --compass --sourcemap --watch . 
>>> Sass is watching for changes. Press Ctrl-C to stop.
  overwrite ./styles/print.css
  overwrite ./styles/print.css.map
WARNING: Couldn't determine public URL for "sprite/*.png" while generating sourcemap.
  Without a public URL, there's nothing for the source map to link to.
  Custom importers should define the #public_url method.

  overwrite ./styles/screen.css
  overwrite ./styles/screen.css.map
$ 

It just compiles once and that's all... Updating the listen submodule to 1.0.3 after making this change doesn't help either.

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol Apr 29, 2013

BTW, I guess the major problem here is SASS picks up the globally installed listen instead of preferring its local copy...

mgol commented Apr 29, 2013

BTW, I guess the major problem here is SASS picks up the globally installed listen instead of preferring its local copy...

@jaredbeck

This comment has been minimized.

Show comment
Hide comment
@jaredbeck

jaredbeck May 2, 2013

As a workaround, downgrading listen worked for me.

gem uninstall listen -v 1.0.3
gem install listen -v 0.7.3

jaredbeck commented May 2, 2013

As a workaround, downgrading listen worked for me.

gem uninstall listen -v 1.0.3
gem install listen -v 0.7.3
@ya7ya

This comment has been minimized.

Show comment
Hide comment
@ya7ya

ya7ya May 3, 2013

@jaredbeck the downgrading worked for me , Thanks for the Tip 👍

ya7ya commented May 3, 2013

@jaredbeck the downgrading worked for me , Thanks for the Tip 👍

@athaeryn

This comment has been minimized.

Show comment
Hide comment
@athaeryn

athaeryn May 3, 2013

Yeah, that's a workaround, but it would be nice to fix the real issue and have sass use its own copy of listen, as @mzgol mentioned. Some people might not be able to uninstall listen-1.0.3 without breaking other things.

athaeryn commented May 3, 2013

Yeah, that's a workaround, but it would be nice to fix the real issue and have sass use its own copy of listen, as @mzgol mentioned. Some people might not be able to uninstall listen-1.0.3 without breaking other things.

@cat-topanga

This comment has been minimized.

Show comment
Hide comment
@cat-topanga

cat-topanga May 3, 2013

Was using Linux Mint new install with Ruby 1.9.3 .
sass did compile but exited right afterwards with the Listener deprecated thing.
Downgrading worked here too so thanks,

cat-topanga commented May 3, 2013

Was using Linux Mint new install with Ruby 1.9.3 .
sass did compile but exited right afterwards with the Listener deprecated thing.
Downgrading worked here too so thanks,

@ahmedelgabri

This comment has been minimized.

Show comment
Hide comment
@ahmedelgabri

ahmedelgabri May 5, 2013

The workaround works if you are not using any other gems that depends on Listen 1.0.3 for example if you are using Guard 1.8.0 this might be a problem.

guard-1.8.0 depends on listen (>= 1.0.0)
If you remove this gem, these dependencies will not be met.
Continue with Uninstall? [yN]

ahmedelgabri commented May 5, 2013

The workaround works if you are not using any other gems that depends on Listen 1.0.3 for example if you are using Guard 1.8.0 this might be a problem.

guard-1.8.0 depends on listen (>= 1.0.0)
If you remove this gem, these dependencies will not be met.
Continue with Uninstall? [yN]
@18601673727

This comment has been minimized.

Show comment
Hide comment
@18601673727

18601673727 commented May 7, 2013

@jaredbeck thanks a lot !

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 May 10, 2013

Contributor

@mzgol wrote:
BTW, I guess the major problem here is SASS picks up the globally installed listen instead of preferring its local copy...

This is the intended behavior.

I'll work on getting Sass compatible with listen >= 1.0.0.

Contributor

nex3 commented May 10, 2013

@mzgol wrote:
BTW, I guess the major problem here is SASS picks up the globally installed listen instead of preferring its local copy...

This is the intended behavior.

I'll work on getting Sass compatible with listen >= 1.0.0.

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 May 10, 2013

Contributor

It looks like listen 1.0.0 has some serious bugs/feature regressions (guard/listen#111 and guard/listen#112) that make it difficult to make it compatible with Sass without drastically increasing the surface area of our integration code. As such, for now I'm going to make Sass compatible only with listen 0.7.x.

Contributor

nex3 commented May 10, 2013

It looks like listen 1.0.0 has some serious bugs/feature regressions (guard/listen#111 and guard/listen#112) that make it difficult to make it compatible with Sass without drastically increasing the surface area of our integration code. As such, for now I'm going to make Sass compatible only with listen 0.7.x.

@nex3 nex3 closed this in bea480b May 10, 2013

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol May 22, 2013

If SASS wants to hold onto the older listen, it really needs to not just use the default one. Now every time I update my gems, SASS breaks and I have to revert listen. Some packages might depend on listen >= 1.0 which makes them impossible to be used in the system at the same time as SASS... This is a big problem IMO.

mgol commented May 22, 2013

If SASS wants to hold onto the older listen, it really needs to not just use the default one. Now every time I update my gems, SASS breaks and I have to revert listen. Some packages might depend on listen >= 1.0 which makes them impossible to be used in the system at the same time as SASS... This is a big problem IMO.

@varemenos

This comment has been minimized.

Show comment
Hide comment
@varemenos

varemenos May 23, 2013

If SASS wants to hold onto the older listen, it really needs to not just use the default one. Now every time I update my gems, SASS breaks and I have to revert listen. Some packages might depend on listen >= 1.0 which makes them impossible to be used in the system at the same time as SASS... This is a big problem IMO.

👍

varemenos commented May 23, 2013

If SASS wants to hold onto the older listen, it really needs to not just use the default one. Now every time I update my gems, SASS breaks and I have to revert listen. Some packages might depend on listen >= 1.0 which makes them impossible to be used in the system at the same time as SASS... This is a big problem IMO.

👍

@chriseppstein

This comment has been minimized.

Show comment
Hide comment
@chriseppstein

chriseppstein May 23, 2013

Member

Our listen dependency should be declared in our gemspec so that the version can be resolved correctly by tools like bundler. Also, @nex3, what is needed to support the more recent API? Is there an issue tracking that?

Member

chriseppstein commented May 23, 2013

Our listen dependency should be declared in our gemspec so that the version can be resolved correctly by tools like bundler. Also, @nex3, what is needed to support the more recent API? Is there an issue tracking that?

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 May 23, 2013

Contributor

bea480b, which closed the issue, makes sure Sass stable won't load listen >= 1.0. 4738115 stops bundling it on master, and declares a version constraint that excludes listen >= 1.0. There should be no way to use the wrong listen version now.

@chriseppstein guard/listen#112 has been fixed, but guard/listen#111 is still blocking our use of listen.

Contributor

nex3 commented May 23, 2013

bea480b, which closed the issue, makes sure Sass stable won't load listen >= 1.0. 4738115 stops bundling it on master, and declares a version constraint that excludes listen >= 1.0. There should be no way to use the wrong listen version now.

@chriseppstein guard/listen#112 has been fixed, but guard/listen#111 is still blocking our use of listen.

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol May 24, 2013

Well, am I using it wrong? I have the /DIR/sass/bin directory from this repository added to path and I still get an error:

$ sass --compass --sourcemap --watch . --trace
>>> Sass is watching for changes. Press Ctrl-C to stop.
/DIR/sass/bin/../lib/sass/plugin/compiler.rb:229:in `watch': uninitialized constant Listen::MultiListener (NameError)
    from /DIR/sass/bin/../lib/sass/plugin.rb:107:in `send'
    from /DIR/sass/bin/../lib/sass/plugin.rb:107:in `method_missing'
    from /DIR/sass/bin/../lib/sass/exec.rb:482:in `watch_or_update'
    from /DIR/sass/bin/../lib/sass/exec.rb:324:in `process_result'
    from /DIR/sass/bin/../lib/sass/exec.rb:41:in `parse'
    from /DIR/sass/bin/../lib/sass/exec.rb:21:in `parse!'
    from /DIR/sass/bin/sass:9

I have both listen 1.1.3 and 0.7.2 installed.

mgol commented May 24, 2013

Well, am I using it wrong? I have the /DIR/sass/bin directory from this repository added to path and I still get an error:

$ sass --compass --sourcemap --watch . --trace
>>> Sass is watching for changes. Press Ctrl-C to stop.
/DIR/sass/bin/../lib/sass/plugin/compiler.rb:229:in `watch': uninitialized constant Listen::MultiListener (NameError)
    from /DIR/sass/bin/../lib/sass/plugin.rb:107:in `send'
    from /DIR/sass/bin/../lib/sass/plugin.rb:107:in `method_missing'
    from /DIR/sass/bin/../lib/sass/exec.rb:482:in `watch_or_update'
    from /DIR/sass/bin/../lib/sass/exec.rb:324:in `process_result'
    from /DIR/sass/bin/../lib/sass/exec.rb:41:in `parse'
    from /DIR/sass/bin/../lib/sass/exec.rb:21:in `parse!'
    from /DIR/sass/bin/sass:9

I have both listen 1.1.3 and 0.7.2 installed.

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 May 24, 2013

Contributor

Are you using the master branch? Currently it only declares its dependencies in the gemspec, so if you're running from the repo it might activate listen 1.x.

Chris is working on adding compatibility with 1.x, so we'll probably just do that rather than try to add a runtime gem version constraint in master.

Contributor

nex3 commented May 24, 2013

Are you using the master branch? Currently it only declares its dependencies in the gemspec, so if you're running from the repo it might activate listen 1.x.

Chris is working on adding compatibility with 1.x, so we'll probably just do that rather than try to add a runtime gem version constraint in master.

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol May 27, 2013

Yeah, that was the master branch. OK, since compatibility with 1.x is planned, I'll just live with it, it's temporary after all.

mgol commented May 27, 2013

Yeah, that was the master branch. OK, since compatibility with 1.x is planned, I'll just live with it, it's temporary after all.

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol Jun 3, 2013

I build and installed the gem to try to use it as intended but then current master doesn't work with either stable or bleeding-edge compass. :( SASS can't find Compass 0.12.2 at all and with the version from master there's listen version conflict (0.7.3 vs. 1.0.0):

/Library/Ruby/Site/1.8/rubygems/specification.rb:774:in `activate_dependencies': can't satisfy 'listen (~> 1.0.0)', already activated 'listen-0.7.3' (Gem::LoadError)
    from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:in `each'
    from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:in `activate_dependencies'
    from /Library/Ruby/Site/1.8/rubygems/specification.rb:750:in `activate'
    from /Library/Ruby/Site/1.8/rubygems.rb:1232:in `gem'
    from /usr/local/bin/compass:22

Is there anyway to bypass that? I need SASS, Compass & source map support which is hard to do in this situation.

Are there any time frames for releasing SASS 0.3.3 stable?

EDIT: I guess that's related to #764?

EDIT2: if anyone has a similar problem, SASS from commit c2ce041 works with stable Compass

mgol commented Jun 3, 2013

I build and installed the gem to try to use it as intended but then current master doesn't work with either stable or bleeding-edge compass. :( SASS can't find Compass 0.12.2 at all and with the version from master there's listen version conflict (0.7.3 vs. 1.0.0):

/Library/Ruby/Site/1.8/rubygems/specification.rb:774:in `activate_dependencies': can't satisfy 'listen (~> 1.0.0)', already activated 'listen-0.7.3' (Gem::LoadError)
    from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:in `each'
    from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:in `activate_dependencies'
    from /Library/Ruby/Site/1.8/rubygems/specification.rb:750:in `activate'
    from /Library/Ruby/Site/1.8/rubygems.rb:1232:in `gem'
    from /usr/local/bin/compass:22

Is there anyway to bypass that? I need SASS, Compass & source map support which is hard to do in this situation.

Are there any time frames for releasing SASS 0.3.3 stable?

EDIT: I guess that's related to #764?

EDIT2: if anyone has a similar problem, SASS from commit c2ce041 works with stable Compass

@chriseppstein

This comment has been minimized.

Show comment
Hide comment
@chriseppstein

chriseppstein Jun 3, 2013

Member

I'm working on the listen issue. I have pull request open for sass and a
patch in progress for compass.

On Mon, Jun 3, 2013 at 1:32 PM, Michał Gołębiowski <notifications@github.com

wrote:

I build and installed the gem to try to use it as intended but then
current master doesn't work with either stable or bleeding-edge compass. :(
SASS can't find Compass 0.12.2 at all and with the version from master
there's listen version conflict (0.7.3 vs. 1.0.0):

/Library/Ruby/Site/1.8/rubygems/specification.rb:774:in activate_dependencies': can't satisfy 'listen (~> 1.0.0)', already activated 'listen-0.7.3' (Gem::LoadError) from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:ineach'
from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:in activate_dependencies' from /Library/Ruby/Site/1.8/rubygems/specification.rb:750:inactivate'
from /Library/Ruby/Site/1.8/rubygems.rb:1232:in `gem'
from /usr/local/bin/compass:22

Is there anyway to bypass that? I need SASS, Compass & source map support
which is hard to do in this situation.

Are there any time frames for releasing SASS 0.3.3 stable?


Reply to this email directly or view it on GitHubhttps://github.com/nex3/sass/issues/719#issuecomment-18869046
.

Member

chriseppstein commented Jun 3, 2013

I'm working on the listen issue. I have pull request open for sass and a
patch in progress for compass.

On Mon, Jun 3, 2013 at 1:32 PM, Michał Gołębiowski <notifications@github.com

wrote:

I build and installed the gem to try to use it as intended but then
current master doesn't work with either stable or bleeding-edge compass. :(
SASS can't find Compass 0.12.2 at all and with the version from master
there's listen version conflict (0.7.3 vs. 1.0.0):

/Library/Ruby/Site/1.8/rubygems/specification.rb:774:in activate_dependencies': can't satisfy 'listen (~> 1.0.0)', already activated 'listen-0.7.3' (Gem::LoadError) from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:ineach'
from /Library/Ruby/Site/1.8/rubygems/specification.rb:766:in activate_dependencies' from /Library/Ruby/Site/1.8/rubygems/specification.rb:750:inactivate'
from /Library/Ruby/Site/1.8/rubygems.rb:1232:in `gem'
from /usr/local/bin/compass:22

Is there anyway to bypass that? I need SASS, Compass & source map support
which is hard to do in this situation.

Are there any time frames for releasing SASS 0.3.3 stable?


Reply to this email directly or view it on GitHubhttps://github.com/nex3/sass/issues/719#issuecomment-18869046
.

@Apathetic012

This comment has been minimized.

Show comment
Hide comment
@Apathetic012

Apathetic012 Sep 13, 2013

any progress? I'm pulling guard from github and i'm having version conflicts:

Bundler could not find compatible versions for gem "listen":
  In Gemfile:
    guard (>= 0) x86-mingw32 depends on
      listen (>= 1.0.0) x86-mingw32

    sass (= 3.3.0.alpha.149) x86-mingw32 depends on
      listen (0.7.3)

Apathetic012 commented Sep 13, 2013

any progress? I'm pulling guard from github and i'm having version conflicts:

Bundler could not find compatible versions for gem "listen":
  In Gemfile:
    guard (>= 0) x86-mingw32 depends on
      listen (>= 1.0.0) x86-mingw32

    sass (= 3.3.0.alpha.149) x86-mingw32 depends on
      listen (0.7.3)
@bennidhamma

This comment has been minimized.

Show comment
Hide comment
@bennidhamma

bennidhamma Dec 12, 2013

I just installed a new laptop with Ubuntu 13.10 out of the box and get this error. Can someone please explain what the proper fix is I need to make? I downgraded listen to 0.7, but then I think a different package updated it again, and broke sass a second time.

bennidhamma commented Dec 12, 2013

I just installed a new laptop with Ubuntu 13.10 out of the box and get this error. Can someone please explain what the proper fix is I need to make? I downgraded listen to 0.7, but then I think a different package updated it again, and broke sass a second time.

@bennidhamma

This comment has been minimized.

Show comment
Hide comment
@bennidhamma

bennidhamma Dec 12, 2013

can grunt watch a directory of sass source files and create the css as I
save my files?

On Thu, Dec 12, 2013 at 3:00 AM, vohof notifications@github.com wrote:

Use grunt, it's much faster.


Reply to this email directly or view it on GitHubhttps://github.com/nex3/sass/issues/719#issuecomment-30406732
.

ben

bennidhamma commented Dec 12, 2013

can grunt watch a directory of sass source files and create the css as I
save my files?

On Thu, Dec 12, 2013 at 3:00 AM, vohof notifications@github.com wrote:

Use grunt, it's much faster.


Reply to this email directly or view it on GitHubhttps://github.com/nex3/sass/issues/719#issuecomment-30406732
.

ben

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol Dec 12, 2013

@bennidhamma Yes. See README for grunt-contrib-sass (or grunt-contrib-compass if you also use compass).

mgol commented Dec 12, 2013

@bennidhamma Yes. See README for grunt-contrib-sass (or grunt-contrib-compass if you also use compass).

@bennidhamma

This comment has been minimized.

Show comment
Hide comment
@bennidhamma

bennidhamma Dec 12, 2013

OK will do thanks guys.
On Dec 12, 2013 8:03 AM, "Michał Gołębiowski" notifications@github.com
wrote:

@bennidhamma https://github.com/bennidhamma Yes. See README for
grunt-contrib-sass (or grunt-contrib-compass if you also use compass).


Reply to this email directly or view it on GitHubhttps://github.com/nex3/sass/issues/719#issuecomment-30424016
.

bennidhamma commented Dec 12, 2013

OK will do thanks guys.
On Dec 12, 2013 8:03 AM, "Michał Gołębiowski" notifications@github.com
wrote:

@bennidhamma https://github.com/bennidhamma Yes. See README for
grunt-contrib-sass (or grunt-contrib-compass if you also use compass).


Reply to this email directly or view it on GitHubhttps://github.com/nex3/sass/issues/719#issuecomment-30424016
.

@monuzira

This comment has been minimized.

Show comment
Hide comment
@monuzira

monuzira May 30, 2016

Hello ,please help me.My .scss file is not working.What can be issue.

monuzira commented May 30, 2016

Hello ,please help me.My .scss file is not working.What can be issue.

@nishantkumar155

This comment has been minimized.

Show comment
Hide comment
@nishantkumar155

nishantkumar155 Feb 21, 2017

Hello please help me i was using this command to compile sass
[ sass --watch saas/style.scss:stylesheets/style.css] but i am getting below error message

Sass is watching for changes. Press Ctrl-C to stop.
error No such file or directory @ rb_sysopen - saas/style.scss

nishantkumar155 commented Feb 21, 2017

Hello please help me i was using this command to compile sass
[ sass --watch saas/style.scss:stylesheets/style.css] but i am getting below error message

Sass is watching for changes. Press Ctrl-C to stop.
error No such file or directory @ rb_sysopen - saas/style.scss

@serter95

This comment has been minimized.

Show comment
Hide comment
@serter95

serter95 Jan 29, 2018

Hello, I am from Venezuela and i have this error:

serter@serter-VIT-P2400:/var/www/html/opencharity/src/css$ sass --watch index.scss:index.css

Sass is watching for changes. Press Ctrl-C to stop.

FATAL: Listen error: unable to monitor directories for changes.

Visit https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers for info on how to fix this.

serter@serter-VIT-P2400:/var/www/html/opencharity/src/css$

Any Idea how to solve it?

it is the first time that hapend to me

serter95 commented Jan 29, 2018

Hello, I am from Venezuela and i have this error:

serter@serter-VIT-P2400:/var/www/html/opencharity/src/css$ sass --watch index.scss:index.css

Sass is watching for changes. Press Ctrl-C to stop.

FATAL: Listen error: unable to monitor directories for changes.

Visit https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers for info on how to fix this.

serter@serter-VIT-P2400:/var/www/html/opencharity/src/css$

Any Idea how to solve it?

it is the first time that hapend to me

@serter95

This comment has been minimized.

Show comment
Hide comment
@serter95

serter95 Jan 29, 2018

I solved runnig this commad

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

i hope that help someone

serter95 commented Jan 29, 2018

I solved runnig this commad

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

i hope that help someone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment