Allow configuration of common paths in "mimosa new"

[kbaltrinic]

Personally I like shorter directory names, so I would prefer to use js and css in lieu of the Mimosa defaults of javascripts and stylesheets. The problem is, there is no way to set this up in advance. Rather after doing a "mimosa new", one must update mimosa-config, plus root out all the affected pre-generated files (jade templates, etc. etc.). It would be nice if these paths could be added to the list of prompts that mimosa asks for when newing up a project.

[dbashford]

Sensible request. 👍

[kbaltrinic]

Just as an FYI, the config values that seem most likely candidates for this treatment are:

watch:
    sourceDir:
    compiledDir:
    javascriptDir:
  vendor:
    javascripts: 
    stylesheets:
bower:  #I realize this will be tricky since its a plug-in 
  copy:
    outRoot:

Perhaps I am getting a little carried a way here but what would be really cool is if I could create my mimosa-config.coffee file ahead of time (or say copy one from another project) and have mimosa pick it up and figure out what to do based on it. Maybe even put my answers to all the standard questions in the config too so I can do a headless "mimosa new." Just thinking out loud here...

[Anachron]

At least allow this with an additional flag like -p or --paths.