[EMAIL PROTECTED] writes:
> 2) which is why global config files in the ~/.gnucash directory
> should over-ride anything in /etc
If they don't already, they're supposed to. It was my intention that
you could completely change the behavior if you wanted by overriding
whatever you liked in ~/.gnucash/config.user, and if you want to
ignore the system file entirely, you could change --config-dir to
point somewhere else, or copy and modify your own bootstrap.scm and
change GNC_BOOTSTRAP. If we need it, I guess we could also add a
--no-site-file like emacs. That wouldn't be hard at all.
However, I think the right thing to do first is to look at
startup-design.txt and then come up with a coherent plan for the whole
startup procedure if it needs to be changed. There are a number of
non-trivial ordering/bootstrapping concerns related to when you
process the args vs loading code vs loading startup files. For
example, the fact that I wanted to allow some things to take effect
*really* early, but not have to completely process arguments twice
(once in C and once in scheme) is what lead to the use of the
environment variables instead of command-line arguments for some
purposes.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
