I recently installed Nim using the windows 64-bit installer. I wrote a hello-world program (just an echo statement). The program compiles and runs when I compile it from the NIM command prompt. Now I'm trying to run it from inside aporia, to see if I can get aporia to work.
Issue #1: When I start aporia using the shortcut in the windows start menu, it asks me to show it the location of NIM.EXE. I do, but the compile immediately fails (exit code 1, no other error message visible in aporia). On the other hand, if I start aporia by opening the Nim command prompt, and then I browse until I find APORIA.EXE, and invoke it manually, aporia compiles my program successfully (exit code 0). I believe that what is happening is that NIM is not in the system's PATH environment variable. Launching the NIM command prompt sets the environment variable correctly, but only within that window. Issue #2: When I use aporia to run my program, it pops open a command prompt. I can only assume that my hello world program is printing into the window, but the window closes so fast that I would never know. I feel that the default behavior needs to be to leave the window open. Issue #3: When I use aporia to compile, if my program contains a deliberately-introduced error, the error message doesn't end up in the errors tab. The error message is completely invisible. Neither of these issues is a show-stopper for somebody like me, who is already enthusiastic about Nim. But they might deter somebody who is evaluating Nim and who isn't sure whether Nim is ready for prime-time.
