`$PATH` only present when Atom is launched from command line

dmnd commented 10 years ago

When Atom is launched from the command line with atom, it has access to $PATH as defined by the shell so the linter can often find executables.

But if Atom is launched via the dock, Spotlight, Applications folder, or other GUI method, it does not inherit $PATH. This means that linters will fail to find their executables. I bet this problem is behind a lot of the bug reports that see the spawn ENOENT message.

rodrigoSyscop commented 9 years ago

As jjoedouglas said, just edit ~/.atom/init.coffee. Go to menu Atom > Open Your Init Script, just add this lines at the end of the file:

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

Works for me.

tr33m4n commented 9 years ago

Just FYI, under Linux/Ubuntu I had to add /bin to the path:

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

Otherwise certain elements of the settings page wouldn't work correctly, such as searching for a package to install (would throw an error saying it could not find uname)

Cheers Dan

Trefex commented 9 years ago

Adding

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

to .atom/init.coffee fixed the issue for me.

:+1:

bee-git commented 9 years ago

Using Atom 0.198.0 on Windows 8.1 Professional together with XAMPP. Trying to use linter-php.

Have entered the following line at the end of .atom/init.coffee

process.env.PATH = ["C:/PortableApps/XAMPP/App/xampp/php", process.env.PATH].join(":")

With this entered, and if the linter detects an error, I get this error message:

'php' could not be spawned. Is it installed and on your path? 
If so please open an issue on the package spawning the process.

with a "Uncaught Error: spawn php ENOENT" in the log file.

I tried adding the following lines to the .atom/config.cson file:

"linter-php":
    phpExecutablePath: "C:/PortableApps/XAMPP/App/xampp/php/"

in addition to the entry in the .atom/init.coffee file that I mentioned above, but that didn't eliminate the problem.

In other words, the problems that others have mentioned in this thread seem to still be occurring in the version of the linter that I'm using on Windows 8.1, and the proposed workarounds don't seem to solve the problem.

UPDATE (2015-05-15) - Checked to see if this problem could be addressed by adding the directory with the php executable to the overall system PATH variable. Doing that does, in fact, address the problem - the linter then works correctly. The PATH variable can be changed using "View Advanced System Settings", which brings up the "System Properties" dialog, and the PATH variable can be changed for either the user or the system by clicking on the "Environment Variables" button and editing the PATH variable contents and then saving the changes.

jean-io commented 9 years ago

Path should contain only directory, right? not a binary like php, so try this:

process.env.PATH = ["C:/PortableApps/XAMPP/App/xampp/", process.env.PATH].join(":")

bee-git commented 9 years ago

@Ricain - Thank you for the suggestion. However, C:/PortableApps/XAMPP/App/xampp/php/ is, in fact, the directory where the php executable php.exe is located. That is, the fully specified path and file name of the php executable is

C:/PortableApps/XAMPP/App/xampp/php/php.exe

As I mentioned in the update to my original post, the problem can be solved by placing the path for the php executable in the system PATH variable. But that really shouldn't be necessary given the configuration and init script options that are supposed to allow you to specify where the executable is located.

beck commented 9 years ago

Has anyone else noticed that when you checkout a different branch (in a project dir already opened in atom), the path is destroyed? Thus in turn, breaking linter.

chrisandrewcl commented 9 years ago

Hey guys,

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

also tried

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

to my ~/.atom/init.coffee didn't work. I also noted that Atom when started from command line works fine but didn't when started from my Xubuntu panel, so I edited the Atom shortcut (laucher) in my panel and changed the command from /opt/atom/atom %F to bash --login -c "atom", as suggested above.

Now all my ruby related packages are working!

davidawad commented 9 years ago

@Trefex THANK YOUUUU. YOU HAVE SOLVED MY LIFELONG STRUGGLE WITH THIS EDITOR.

ssfrr commented 9 years ago

It seems that init.coffee isn't run until after packages are loaded, so if one of your packages tries to spawn a shell command that's not on your default $PATH then it still doesn't work. As fas as I can tell the only alternative in that case is tweaking the launcher to run Atom from within a shell environment.

rennsport commented 9 years ago

I'm running OS X 10.10.5 and Atom 1.0.9 and I'm having this issue both launching from GUI and terminal. Are there any other solutions other than editing the init.coffee because that doesn't seem to work for me.