Closed TattdCodeMonkey closed 9 years ago
Please try if there's any difference in new version. I couldn't reproduce the error on any of my machines
I'll update and see if this changes anything. Still happens.
I think this is an atom issue. If I open atom from the command-line it works fine. Opening from Taskbar, Lauchpad or spotlight I see the above error. Its something weird with atom not loading PATH unless its opened from the terminal.
It might be something about node's child_process.spawn method. I've changed it to BufferedProcess of atom API
2015-05-19 16:14 GMT+02:00 Rodney Norris notifications@github.com:
I'll update and see if this changes anything.
I think this is an atom issue. If I open atom from the command-line it works fine. Opening from Taskbar, Lauchpad or spotlight I see the above error. Its something weird with atom not loading PATH unless its opened from the terminal.
— Reply to this email directly or view it on GitHub https://github.com/iraasta/autocomplete-elixir/issues/5#issuecomment-103514572 .
Krzysztof Wende Neon Tree Solutions Ltd. http://neontree.pl
With
autocomplete-elixir
package enabled I receive an uncaught error whenever I save an elixir file. I've seen this on two different machines. one running OSX 10.10.2 and another running 10.9Steps to Reproduce
Atom Version: 0.190.0 System: Mac OS X 10.10.2 Thrown From: autocomplete-elixir package, v1.2.4
Stack Trace
Uncaught Error: This socket is closed.
Commands
Config
Installed Packages