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

nimble install <package> results in git error "Too many arguments" with exit code 129 #1229

Open
PixelSymbols opened this issue Jun 24, 2024 · 1 comment

Comments

@PixelSymbols
Copy link

PixelSymbols commented Jun 24, 2024

os: windows
git: 2.41.0, 2.45.2
nimble: v0.14.2
nim: 2.0.6 stable
choosenim: v0.8.4

Cannot install any existing package using nimble install
example:

D:\Documents REALLY\Programming\language\Nim\first>nimble install mummy
Downloading https://github.com/guzba/mummy using git
       Tip: 3 messages have been suppressed, use --verbose to show them.
tools.nim(62)            tryDoCmdEx

    Error:  Execution of 'git clone --config core.autocrlf=false --config core.eol=lf --recursive --depth 1 -b 0.4.2 https://github.com/guzba/mummy W:\temp files\nimble_2108\githubcom_guzbamummy' failed with an exit code 129.
        ... Details: fatal: Too many arguments.

issue is in the path where nimble downloads it. It supposed to download into temp files directory, and originally it would do it just fine, because temp files folder by default made by system.
But i changed my temp folder path in system path variables, and it contains spaces. Because of this, git thinks that space devides single path into 2 arguments.
Nimble, when using git, should/must wrap path in quotes to prevent such error from happening, either always, or when it finds spaces in path.
Hoping for fix ❤

@AMSwift73
Copy link

I also have a username (Windows 10) with a space, and this also kills Nimble 2.2.X install functionality for me.

I tried putting an alternative .nimble/bin directory in my PATH system environment variable, and also setting a new TEMP directory, but even with both changes nimble kept using /.nimble

So I downgraded to Nim (and Nimble) 2.0.X. This works for me - Nimble 2.0.2 uses (reads?) an 8-character shortened version of the username that does not contain spaces.

So, repeating the request.
Also, if there is a nimble master config file somewhere that lets users control which directories are used by nimble for various things, that would allow ppl to choose a larger, faster HHD if so desired. This is especially useful for storing large, complex libraries.

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

2 participants