-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Doesn't work on Windows #8
Comments
Same here. I get the following error: C:\path> wicked --toc --nocommit
info wicked Cloning wiki from [email protected]:user/myrepo.wiki.git
Cloning into 'wiki'...
remote: Counting objects: 3, done.
remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
Receiving objects: 100% (3/3), done.
Checking connectivity... done.
child_process.js:1162
throw errnoException(err, 'spawn');
^
Error: spawn UNKNOWN
at exports._errnoException (util.js:746:11)
at ChildProcess.spawn (child_process.js:1162:11)
at exports.spawn (child_process.js:995:9)
at run (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\run.js:27:14)
at runJsdoc (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\run-jsdoc.js:44:3)
at runnel (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\node_modules\runnel\index.js:77:10)
at updateWiki (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\index.js:77:5)
at C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\index.js:82:5
at C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\clone-wiki.js:65:7
at C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\clone-wiki.js:37:7 I'm using: Win7 x64 |
I'm getting this too. This is caused by "directly" spawning the BTW this works on Unix because of the hashbang. |
Line 44 in b87d276
can be replaced by :
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lib/run.js
needs os awareness hacked in such as here: https://github.com/Concurix/concurixjs/commit/70fcdf5207af955af266d328f45bc14d03275341child-process
does not work on Windows, among other things, but at the moment I get the "errno 193" problem right after the git checkout succeeds.The text was updated successfully, but these errors were encountered: