Now that Nimble offers nimscript I actually think it should be the other way 
around. `config.nims` should be deprecated. This may sound crazy, but I don't 
see why we should have two tools that offer the same functionality. The nim.cfg 
format works incredibly well for configuring the compiler and I am yet to run 
into a use case where I need to use full-blown Nim when I'm configuring Nim...

Reply via email to