Christopher Browne <[EMAIL PROTECTED]> writes:
> I don't think it'll be too difficult to ask/answer the questions
> relevant to making sure we know which ordering is most appropriate.
>
> In either case, we can have a reasonably logical way of either:
> a) Sequencing which set of configuration to load in next, such as
> /etc/gnucash.conf, /usr/local/etc/gnucash.conf,
> $HOME/.gnucash/gnucash.conf, ./.gnucash/gnucash.conf
> or
>
> b) Setting up a list like the above, and traversing it in reverse
> order, stopping as soon as a config file is found.
I had planned for us to have a setup like (a) rather than (b). I
wanted the process to be (assuming /etc/ for
sysconfigdir):
(1) load "/etc/gnucash/config"
(2) load-if-exists ~/.gnucash/config.user
else load-if-exists ~/.gnucash/config.auto
So the system config file is *always* loaded, and then the user's
hand-wrought config file (like a .emacs) is loaded if it exists. If
it doesn't exist, then the automatically generated config file is
loaded, if it exists. This is how things were working last time I
looked, and it's what I intended and documented in startup-design.txt.
The reason to handle (2) in the way indicated is that this allows the
user who decided to create their own config file to have control over
where (if at all) the automatically generated stuff gets loaded. By
default, most users should put a (gnc:load-auto-config) into their
config.user, if they create a config.user.
(Note that I just realized that we don't have a gnc:load-auto-config
function. I need to add one. I also need to put the info above into
the docs somewhere...)
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
