-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
atlas cmd writes nim.cfg to wrong destination: cannot open: balls/nim.cfg [IOError] #18751
Comments
It should really write to |
since you've closed this issue, I have to assume that crashing with (that command came from |
I don't know why it could not write into this directory, but it should write into $nim/balls/nim.cfg, as documented. |
because it creates $nim/../balls ... |
Example
Current Output
[Warning] (nim-bytes2human) package has no tagged releases
/private/tmp/d04/foo2/Nim/tools/atlas/atlas.nim(473) atlas
/private/tmp/d04/foo2/Nim/tools/atlas/atlas.nim(456) main
/private/tmp/d04/foo2/Nim/tools/atlas/atlas.nim(396) patchNimCfg
/private/tmp/d04/foo2/Nim/lib/system/io.nim(866) writeFile
Error: unhandled exception: cannot open: balls/nim.cfg [IOError]
Error: execution of an external program failed: '/private/tmp/d04/foo2/Nim/tools/atlas/atlas clone https://github.com/disruptek/balls'
Expected Output
should write to $nim/config/nim.cfg, not $nim/balls/nim.cfg,
Example 2
bin/nim c -r tools/atlas/atlas.nim clone cligen
Error: unhandled exception: cannot open: cligen/nim.cfg [IOError]
Additional Information
1.5.1 98f7254
The text was updated successfully, but these errors were encountered: