Failed to spawn error with Atom 0.166.0.

[bobrocke]

Error in red dialog box in upper right corner:

Failed to spawn command scss-lint. Make sure scss-lint is installed and on your PATH

This just started with Atom 0.166.0. It didn't so it before.

[bobrocke]

I have the same error with Atom 0.168.0.

I ran which scss-lint and got back /Users/bob/.rvm/gems/ruby-2.0.0-p247@rails3/bin/scss-lint

So I added

'linter-scss-lint':
      'scssLintExecutablePath': '/Users/bob/.rvm/gems/ruby-2.0.0-p247@rails3/bin/scss-lint'

to my Atom config file.

I still get the same error about scss-lint not being installed.

[InSuperposition]

👍
I get a similar error, I am also using RVM.

[karl-wednesday]

I started experiencing the same issue since sometime in early January. Everything seemed to be working fine prior to that.

As far as I'm aware, the only thing that has changed is that I have updated Atom and all of its installed packages using Atom's built in updater, so perhaps the issue was introduced due to the Atom 0.166.0 update as @bobrocke suggests.

Unlike the other reporters, I am using rbenv via Homebrew.

which scss-lint reports that my path is /Users/karl/.rbenv/shims/scss-lint

[bobrocke]

Any progress with this? It's a problem and I don't know of another Atom SCSS linter.

[jclusso]

yea, still waiting on an update for this.

[nickroberts]

I get the same thing on 0.177.0.

[nickroberts]

I started Atom via the command line, and it worked. Odd.

This still should be addressed, me thinks.

Using rvm, as well.

[bobrocke]

Has this plug-in been abandoned?

[bobrocke]

I wonder if anyone using rbenv is having this problem?

[bobrocke]

Yes, I see that @karl-wednesday is using it. Dang.

[InSuperposition]

@nickroberts I get the same results. This issue may directly be related to AtomLinter or Atom Itself. steelbrain/linter#150

[maban]

I'm getting this too. Opening Atom from the command line instead of the dock worked, but it's not an ideal solution.

[simmerz]

Getting this too with rbenv. It looks like it's because Atom is started without the user profile, so the version of ruby it sees isn't the same version that the terminal sees. Hence why starting from the terminal works.

[bobrocke]

@simmerz That's an interesting observation! How can I tell what version Atom finds when started from the terminal? Maybe I can configure scss-lint there?

[bobrocke]

Here's an issue with a resolution that worked for me: #39

[steelbrain]

Fixed by #58

[idmarjr]

Hello guys!
I follow the instructions from readme.md to install linter-scss-lint and looks like this issue is happening again :( (At least for me).

MacOSX 10.11
Atom 1.0.19

Any ideas of how can I fix it?

[Arcanemagus]

@idmarjr OS X "helps" you by striping the environment from any application launched from the GUI. You can either launch Atom from a terminal window, or specify the path the scss-lint in the settings.

[idmarjr]

@Arcanemagus I tried launch it from terminal.app but even this way it still happening. :/

[steelbrain]

@idmarjr try specifying a full path to it in settings.

[idmarjr]

@steelbrain Awesome! It works.
I ran which sass-lint in terminal and than copy the returned path.
Go to Atom > Preferences > Packages > linter-css-lint > Settings and past that path in Executable Path field.

Appreciate your help guys!

[AidenWri]

Suddenly getting this error after upgrading to Atom V1.3.1

[Arcanemagus]

@RhianWright have you tried specifying the full path as outlined a few times in this thread?

[graysonhicks]

Go to Atom > Preferences > Packages > linter-css-lint > Settings and paste that path in Executable Path field.

@steelbrain @idmarjr This works, thanks!

[fahimfarookme]

Apparently the atom-scss-lint does not install the scss-lint gem. Try installing the gem manually.
gem install scss_lint

[Arcanemagus]

@fahimfarookme That's part of the readme's installation steps: https://github.com/AtomLinter/linter-scss-lint#scss-lint-installation 😉.

[webzorg]

RVM case. http://stackoverflow.com/questions/26247926/how-to-solve-usr-bin-env-ruby-executable-hooks-no-such-file-or-directory
which scss-lint, put the path in plugin default executable and change bin with wrappers.