#246 closed task (fixed)
Start using user-specific config files
Reported by: | Philip Taylor | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | |
Component: | Core engine | Keywords: | |
Cc: | Patch: |
Description
Editing system.cfg is nasty, because you get merge conflicts and accidental commits etc. So people should always use user-specific configuration, which looks like it's already implemented in data/profiles/default/settings/user.cfg. So: make sure that actually works, delete the non-default profiles because they're confusing and unneccessary, and update all the relevant documentation (and add a comment in system.cfg) to say to edit user.cfg.
Change History (3)
comment:1 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 5 years ago
From 2008-05-31-QuakeNet-#wfg-Meeting.log
:
19:01 < matei> hey I have another question: is it possible to use user.cfg to override system.cfg (and is it what it already does?) 19:01 < matei> people keep editing and commiting system.cfg 19:01 < matei> I would want to be able to tell them "create a user.cfg and edit that" 19:02 < matei> I believe AOM had this model 19:02 < janwas> matei: i believe that is the original plan. not sure if that works ATM.. 19:02 < matei> okay, might be a small thing to fix before an open source release 19:06 < matei> and btw user.cfg doesn't work
According to the ticket description, this commit fixed user.cfg
.
Everything we can see in the code, especially introduced in that commit, and circumstancial evidence such as trac tickets and IRC logs indicates that people just had a habit of edting the previous system.cfg
(former default.cfg).
Fixed in r6919.