> How did you use it? Was it from a previous installation? What did you run 
> exactly? Please outline explicitly, otherwise I have to guess which is not 
> ideal.

I simply tried to do `choosenim install self`. That throwed that "could not 
load: (libcrypto-1_1-x64|libeay64).dll" error. That is what sent me down this 
rabbit hole.

Regarding the instructions to install choosenim, when I went to the choosenim 
repo, it told me to download the zip file, but when I went to the download page 
and I saw an executable I 
_[think](https://forum.nim-lang.org/postActivity.xml#think) I thought it might 
be an installer which might work better. If you cannot use the bare executable 
to install choosenim, perhaps it should not be there (and before the .zip file 
that you must use)? Perhaps the link should be to the zip file rather than to 
the git repo download page?

I also miss an "update" section on the choosenim documentation and perhaps a 
"what to do when things go wrong" section. I had a non working choosenim 
install. It would have been great to know what to do in that case.

Another thing that I've realized in retrospect is that I completely 
misunderstood the following section on the 1.4.0 announcement blog:

> Existing users > If you have installed a previous version of Nim using 
> choosenim, getting Nim 1.4 is as easy as: > > $ choosenim update self > $ 
> choosenim update stable

I didn't realize that I had to do 
_[both](https://forum.nim-lang.org/postActivity.xml#both) things. It was a dumb 
mistake on my part, but I thought I could do either of those, and I think I 
only did one of them (I don't remember which, I might have tried both at 
different times when it didn't work).

Perhaps we could make a bare "choosenim update" do both or something like that?

IMHO another problem with the nim update instruction is this:

> If you don’t have choosenim, you can follow the same install link as above.

Since choosenim was not working for me, technically "I didn't have choosenim". 
I thought about that but that pointed me to a zip file with a nim folder in it. 
From my perspective that was a completely different kind of installation than 
what I was trying to achieve... I wanted to get nim installed into my existing 
choosenim install, not manually put nim somewhere in my hard drive and manually 
add it to the path. That is why I ended up manually unzipping that folder into 
the .choosenim folder in my profile.

I would say that my biggest mistake was misunderstanding that those 2 choosenim 
commands do different things (the first updates choosenim and the second 
updates nim). 

Reply via email to