Nimscript: the compiler supports a directory wide config.nims file

compiler/nim.nim

@@ -59,6 +59,9 @@ proc handleCmdLine() =
       runNimScript(scriptFile)
       # 'nim foo.nims' means to just run the NimScript file and do nothing more:
       if scriptFile == gProjectFull: return
+    elif fileExists(gProjectPath / "config.nims"):
+      # directory wide NimScript file
+      runNimScript(gProjectPath / "config.nims")
     # now process command line arguments again, because some options in the
     # command line can overwite the config file's settings
     extccomp.initVars()

doc/nims.txt

@@ -9,7 +9,8 @@ system.
 
 So instead of a ``myproject.nim.cfg`` configuration file, you can use
 a ``myproject.nims`` file that simply contains Nim code controlling the
-compilation process.
+compilation process. For a directory wide configuration, use ``config.nims``
+instead of ``nim.cfg``.
 
 The VM cannot deal with ``importc``, the FFI is not available, so there are not
 many stdlib modules that you can use with Nim's VM. However, at least the