Elixir Path is set, but getting error on Atom launch

[krisalyssa]

Mac OS X 10.10.3 atom 0.209.0 autocomplete-elixir 1.3.5 elixir 1.0.4 installed via Homebrew

Elixir Path is set in the autocomplete-elixir settings to /usr/local/bin/elixir, but when I launch Atom [1] I get Uncaught BufferedProcessError: Failed to spawn commandelixir. Make sureelixiris installed and on your PATH

[1] Launching via Quicksilver, which is effectively launching from the Finder. Yes, I know.

Launching Atom from a command prompt does not generate this message. Currently, the README makes it sound like setting Elixir Path is sufficient, but it isn't. Does the documentation need clarification?

[wende]

On it

[TrevorS]

:+1:

[billgloff]

I'm also experiencing this same error with Atom 1.0

[wende]

Yeah. That was pretty embarrasing typo. Setting was called elixrPath, and I was looking for elixirPath. It should work with the newest release

[essenciary]

Still getting the error - searched the plugin's code and there's no typo so it seems I'm using the latest version. Atom 1.0.2.

[borisdamato]

+1 I confirm, it's still happening to me too.

[wende]

No possible fix for MacOS except for launching atom from commandline for now. I've got no idea why it happens

[jameybay]

Same error on Linux also in version 1.0.4.

[essenciary]

In the end I found a very simple workaround - just build a simple Mac app with Automator that launches Atom from the command line and use that from Finder/Spotlight/LaunchBar/etc.

You can download it from here: https://dl.dropboxusercontent.com/u/1081319/Atomico.zip

If you don't trust running apps from strangers (good, cause you shouldn't!), you can build your own in 60 seconds. More details here: http://essenciary.com/how-to-fix-failed-to-spawn-command-elixir-in-atom-for-os-x/

[kristianmandrup]

I now get:

"Failed to spawn command iex. Make sure iex is installed and on your PATH"

11:27 $ atom .
✔ ~/repos/elixir-projs 
11:27 $ $PATH
-bash: //anaconda/bin:/usr/local/bin/:/Users/kristianmandrup/scala-2.11.7/bin:/Users/kristianmandrup/purescript:/Users/kristianmandrup/psc-ide:/Applications/xiki-master/bin:/usr/local/opt/android-sdk/tools:/Users/kristianmandrup/.rvm/gems/ruby-2.3.0/bin:/Users/kristianmandrup/.rvm/gems/ruby-2.3.0@global/bin:/Users/kristianmandrup/.rvm/rubies/ruby-2.3.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/npm/bin:/opt/X11/bin:/usr/local/git/bin:/usr/local/go/bin:/usr/local/MacGPG2/bin:/Users/kristianmandrup/.rvm/bin:/Users/kristianmandrup/npm/bin: No such file or directory
✘-127 ~/repos/elixir-projs 
11:30 $ which iex
/usr/local/bin//iex
✔ ~/repos/elixir-projs
11:29 $ iex
Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Interactive Elixir (1.2.2) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)>

Any ideas?

[wende]

I've added Troubleshooting to the README.md file Please check out if anything works for you from there

[boom0830]

Add this

process.env.PATH = ["/usr/bin",
                    "/usr/local/bin",
                    ].join(":")

to the wrapper.coffee file right after IS_ELIXIR = false and the error went away for me

[simondelacourt]

@boom0830 somehow setting the path from the wrapper.coffee breaks the whole plugin, but no console messages.