I am sorry to bother folks with this here, but I really am having trouble wrapping my head around nimscript.
* 1)If I have foo.nim, and I write foo.nims -- ok, what do I do next? "nim c -r foo.nim" works, but can I run "foo.nims" directly in order to build/run "foo.nim"? Would I want to? * 2) Is there a way to provide a global "nimscript" for a directory, similar to "nim.cfg"? * 3) What is the purpose of the "task" template in nimscript? How do I make a task happen? How can I see a list of the tasks? * 4) Is there a web-page? The nimscript module docs only describe the API, and I do not fully understand some of the magic in the source-code. * 5) What is best-practice? I definitely run nimble at the top, to help folks install and use my libraries. But during development, nimble takes seconds, so I'm thinking it makes sense to use nimscript for tests etc. * 6) The most important thing for me is running "pkg-config", but with caching (which nimscript.exec() can do), and falling back on CFLAGS/LDFLAGS from the shell-environment when pkg-config fails. (Compiling everything via Nim is just not possible for me, so I am willing to be UNIX-centric as a compromise.) Is this a good use-case for nimscript?
