-
Notifications
You must be signed in to change notification settings - Fork 7
Error 'Uncaught Error: spawn pandoc ENOENT' #14
Comments
Have you got your PATH set up correctly? See: Problems with PATH |
I made the change you described; it didn't avoid the problem. (Pandoc is properly installed and in my path.) One thing that does suggest that it might be a path issue of some sort: if I do |
I don't know if this is relevant: I have the same problem on Ubuntu 14.04. So it's not just an OS X quirk. |
I had the same problem, with the same error message as above. To fix it you have to:
Add "env" before this line:
Like so:
Then call atom from the command line. I have yet to make it work by calling atom from spotlight I also tried editing /etc/launchd.conf, adding in
|
I've got the same issue. Will work when I run atom from command line, but not launch as an icon/explorer. I've added "env" and that didn't fix it. Any updates of things to try out? |
I'm afraid not. This is a more general issue with Atom (and Sublime) and Macs, unfortunately. |
I have the same problem, on OS X – even though
Starting Atom from CLI works just fine, oddly. |
Whenever I try to preview I get the error 'Uncaught Error: spawn pandoc ENOENT'. I'm using version 0.1.2, Atom version 0.165.0 on OS X.
Here is the stack trace:
The text was updated successfully, but these errors were encountered: