Nimble does not use the nim in the path even if it fulfills the reqs of the current proyect
Nimble does not seem to use the nim that is on the path even if it matches the deps of your current project. Because of that, if you have installed nim as a package (even if it is indirectly, e.g. if you `nimble install langserver` which locks nim at 2.0.2), nimble prioritizes and uses that nim version (2.0.2 in that example) instead of the nim that is on the path.

This is quite confusing and unexpected. What would happen if for excample you later installed some `randomlib` that locked nim 2.0.0 in its deps, using `nimble install randomlib`? Would nimble suddently start using nim 2.0.0 instead of 2.0.2 when working on arraymancer which did not use `randomlib` in any way? Note that the only reason that arraymancer sets `nim >= 1.0.0` as a req in its nimble file is so that arraymancer can be used with any version of nim, so it is not feasible to change that references to something newer...