Config files for common settings

[GoogleCodeExporter]

(Enhancement Request)

I'd like to see the ability to put my settings in a config file, maybe
~/.gourcerc, that overrode the defaults but would still be overwritable
with command-line arguments.  Better yet, I'd like to see a series of
config where each overrides the last:

/etc/gourcerc  (machine-wide)
~/.gourcerc    (user-specific)
./.gourcerc    (repo-specific)
--             (command-line)

Personally, I'd have things like resolution, speed, and colors in my
user-specific config, hidden users and files in repo-specific configs, and
then would only rarely have to override things with command-line args.

Original issue reported on code.google.com by delive...@gmail.com on 7 Nov 2009 at 1:28

[GoogleCodeExporter]

Cool idea.

Not familiar with the -- idiom, but otherwise sounds good.

Original comment by acaudw...@gmail.com on 9 Nov 2009 at 9:32

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

The -- (double hyphen) would be unnecessary because gource doesn't call any 
other command-line programs. The double hyphen is typically used to tell the 
program to capture-but-ignore everything after the double hyphen and pass it to 
another command-line program that is called.

e.g. build -p "/dev/project1" -- all

build prepares a project, "/dev/project1", before calling make with the all 
command for that project's makefile.

I've also seen a single hyphen used this way. Anyways, back to gource; any 
overriding options could be passed on the command-line without the double 
hyphen preceding them.

Original comment by skoobiedu@gmail.com on 20 Apr 2011 at 1:53