Thanks... see my recent update for a little more clarification. The anomally 
seems center on nimble installs from earlier and currrent version of Nim/Nimble 
... ( _Which does seems very unlikely_ since no-one else is having this 
issue)... but maybe you can find the _hole_ in analysis to date. I am 
suspecting some historically mangled configuration/corruption which I am not 
aware of... but that is just hunch (I did check all paths for possible nim.cfg 
/ nimbledep .... overrides.

Reply via email to