Dominik Picheta

Is this not just a Nim stdlib issue?

I can no longer reproduce this, has it been fixed?

Very unfortunate edge case. I think the only workaround you can use here is to use the old-style .ini-like Nimble file format.

There isn't AFAIK, unless Nim provides that somehow. The best you can do is what I suggested [on irc](https://irclogs.nim-lang.org/18-01-2019.html#15:04:28). Perhaps there is a different reason you want this callback?

`statusContent` is implemented in jester, right? Why not use `unsafeSend` there (for httpbeast only)?

@philip-wernersbach I can easily extend Nimble to support multiple `nimbleDir`'s. I can also add a `--global` flag which will install packages globally to `/usr/lib/nimble/` or something like that. Maybe you...

> The main difference is that Go code can import from URLs (e.g. GitHub), whereas nimble relies on `nimbledata.json` That's incorrect. Firstly, Nimble relies on `packages.json` optionally. Secondly, Nimble does...

You are correct about my desire for simplicity. I am glad that you acknowledge it :) What happens if I have the same package (of two different versions) in my...

> `--global` option？I really don't want it Then you won't have to use it. Simple.

It will solve your problem. The path to where Nimble will install packages globally will be added to Nim's config file by default (once I implement this feature).