Dominik Picheta

I think this might be an issue with this script in case anyone wants to have a look: https://github.com/dom96/choosenim/blob/master/scripts/choosenim-unix-init.sh

My guess is: * Choosenim was installed using the script, it downloaded Nim 1.2.0 * After a few months later the script was run again, it once again installed Nim...

Choosenim doesn't allow you to pass custom flags to Nim for bootstrapping right now, so you'll need to build Nim yourself to get this feature. You can find instructions for...

This could be as simple as making `choosenim 1.6.0 --compileFlag:--incremental:on` (or similar) work. One thing to consider is that most of the time choosenim will download nightlies, you will need...

Weird that it failed the build. But that's a separate issue. The first issue is that it gets the nightly filename incorrectly, the code for that is here: https://github.com/dom96/choosenim/blob/master/src/choosenimpkg/download.nim#L272 So...

I don't think it's uncommon, but I would appreciate your help in diagnosing the cause and maybe even coming up with a PR to fix it :)

IIRC the main reason I chose to do it this way is simplicity, supporting both symlinks and this proxy exe would have been more complex. To be honest I think...

Is this with latest version of choosenim? Can you reproduce it? Does it happen with older versions too?

> how do I build a shim? Can you just grab the choosenim release from the releases page and use it to install Nim somewhere? You can set a new...

Why would you expect that? Choosenim even asked you whether you want to overwrite the `nimble` symlink. If you didn't want that you should have said `N`