Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
+ /* Don't continue adding to this list. When 2.0 rolls around bump
+ the 1.4 (unnumbered) files off the list. */
+ static const gchar *user_config_files[] = {
+ "config-2.0.user", "config-1.8.user", "config-1.6.user",
+ "config.user", "config-2.0.auto", "config-1.8.auto",
+ "config-1.6.auto", "config.auto", NULL};
I think we should separate out the config*.user and config*.auto files
into separate lists and still load config.auto even if it finds a config.user.
config.auto is auto-created by gnucash. config.user is where a user
could theoretically get gnucash to load new files (e.g. new reports).
I say "theoretically" because it might not actually work -- it didn't work
properly in 1.8 -- but it might work in 2.0....
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
