-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
env: node: No such file or directory #32
Comments
For what it's worth, I checked and when I run Option+Shift+C, the final command list it passes to Popen is |
Ok I think I know what is messing this up. Several people have been having similar problems... This has to do with the last commit. |
I don't think this has anything to do with the last commit, because I'm using the version v2013.01.26.20.45.16, from the Sublime Package Manager. The commit you referred to is almost two months newer. This is a very old issue. Speaking of the package manager, you should update the version in the Sublime package manager. |
Ok I'm looking into this now |
Seconded. I'm guessing a lot of people use Homebrew to install Node so a fix would be greatly appreciated. |
+1 |
i can help you debug, but remember I'm using the old v2013.01.26.20.45.16. I just want to compile a single standalone coffeescript file, no build system. Also I noticed a bug that may be related. Every time I run the Build:Run command (which displays a failure report), I notice the path has grown by one "/usr/local/bin:". Repeatedly running the command will add dozens of duplicate "/usr/local/bin:" path elements. |
@alexchandel Help would be appreciated... I believe I added ad function like path resolve to get the absolute path to the file... I think there is an issue there since I think all of this started happening after I added that line. I'm suggesting that the execution of the command is good but resolving the path to the file has problems, hence getting the "no such file/dir" error. I'm open to suggestions about multiple OS compatible path resolve function(s). |
Well something is wrong with the path resolution, because it re-appends the path each time. Since we set the |
I found a partial hardfix. In CoffeeScript.sublime-build, change the
This fixes the Build commands, but does nothing for the Compile command. This tells me the binDir path isn't being added to the Build PATH. Incidentally, the Also, I have a lead for you on Compile commands.
to
makes that snippet runnable when copypasted into the interpreter. The final call ends up being However, and I have no idea why, this completely blows up in Sublime Text. When I run Coffee: Compile File, the console says:
Even trimming the call down to just I'm really not sure what the problem is with the Compile commands. If you have a potential solution, I can test it, but I strongly recommend you investigate this bug, as it probably affects everyone who installs coffeescript/node with homebrew. |
+1 |
+1 I persuaded a friend, a recent Sublime Text 2 convert, to try installing CoffeeScript (he first had to install homebrew, then node via homebrew) and sublime-better-coffeescript. He encountered the exact same issue. He'd never used CoffeeScript before (just JS). This suggests this problem affects everyone who installs node/coffeescript via homebrew. |
I hear you guys! I have been busy with a C# project and will fix this as soon as I can take a break from it. In the meantime if you are able to, send a pull request and I would gladly put it in. Thanks for your interest and I apologize for my absence. |
I kinda fixed the problem by symlink the coffee-script modules from npm directory to /usr/local/bin ln -sv /usr/local/share/npm/lib/node_modules/coffee-script/bin/coffee /usr/local/bin/coffee |
Hopefully not a permanent fix. With the current release build, there's now a |
Should be fixed now with the new settings. Check the |
Still can't get this to work. I keep this in my console when I try to enable watch mode:
In my settings I've tried
and both
and
What's the problem here? |
The problem is the plugin cannot find coffee executable. This may not be related to the plugin itself, so let's try to debug this.
logan@host:~$ npm ls -g | grep coffee
├── coffee-script@1.6.3
├─┬ coffeelint@0.5.6
│ ├── coffee-script@1.6.3
├── UNMET DEPENDENCY generator-coffee *
│ │ ├── coffee-script@1.3.3
logan@host:~$ which coffee
/usr/bin/coffee
Post your findings and I'll help you debug. |
@aponxi Sorry about the delay. I'll be going through your steps later this evening, so I'll report back soon. |
Close for now. |
For someone reason my email update didn't show up here. Following Aponxis instructions, it now seems to be working, so thank you @aponxi . It'd be a great addition to the Readme, as lavrton mentions. |
You are most welcome @zakdances ! I'm happy to hear that you were able to solve your issue. @lavrton I will provide more instructions on those. |
I am running OSX 10.8.2, Sublime Text 2.0.1, sublime-better-coffeescript v2013.01.26.20.45.16, which I installed with Package Control. I tried the following in a file named
script.coffee
:and I obtained:
My
coffee
executable is located at/usr/local/share/npm/bin
, the global location fornpm
whennode
is installed withbrew
, so I set"binDir": "/usr/local/share/npm/bin"
in the settings.My
node
executable is located in/usr/local/bin
, but I can't set that, and I think/usr/local/bin
is already in my Sublime Text 2 path.Pressing Option+Shift+C yields
Compilation failed
in the status bar.If I run the file with Command+Shift+B, I obtain:
And of course Command+B yields:
I don't want to make a Cakefile. I should be able to compile a single
source.coffee
file into something likesource.js
.The text was updated successfully, but these errors were encountered: