> Nimble is responsible only for the creation of a nim.cfg file that points to > the correct location of the installed packages with the standard --path: > option of the compiler (this is done by running nimble setup once within your > project).
>From <https://forum.nim-lang.org/t/8404#54514> > The nimble setup command creates a nimble.paths file containing file system > paths to the dependencies. It also includes the paths file in the config.nims > file (by creating it if it does not already exist) to make them available for > the compiler. >From <https://github.com/nim-lang/nimble#nimble-setup> Yes, but again, this requires setting up a project for every single script that I might want to run. If I understand correctly this means I cannot use `nim c` for anything without first setting up a project. Is my understanding correct?
