Skip to content
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

Failure to spawn certain processes on Windows #2

Closed
jankolkmeier opened this issue Aug 21, 2012 · 2 comments
Closed

Failure to spawn certain processes on Windows #2

jankolkmeier opened this issue Aug 21, 2012 · 2 comments

Comments

@jankolkmeier
Copy link

I am having an issue on windows when trying to spawn ruby processes like compass or sass. I haven't tracked down the exact issue, but it seems related to this: nodejs/node-v0.x-archive#2318

I have applied the proposed fix (commit incoming) and it seems to work well in my case. I don't have time/setup to give a throughout test, though.

@emirotin
Copy link

emirotin commented Oct 5, 2012

same issue here (with docpad-plugin-sass) and I confirm that the fix works for me

@balupton
Copy link
Member

With the just released v1.4.1 you can now use getExecPath to get the full path of an executable, you would then use that path when doing your exec or spawn calls. Will update the docpad plugins to make use of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants