The solution is simple:This is the ideal towards which we strive. But it's not as simple. Trivial example: your Windows and Linux screens have different sizes so the windows (which remember their positions as you've surely noticed) should come up in different places. In fact, this one isn't OS-specific, of course, 2 Windows machines could have the saem difference. But there are more when you start changing OS, for example I use IrfanView to view big images under Windows but xv under Unix. And even though I use vim under both systems, it's located in different places. And so on.
Configure include files!!!
You put the common configurations (accounts, folders, filters) in a common file.
You create TWO configuration files, one for Linux, one for Windows. In each file you include the common part.
Obviously, window positions, helper applications, base directory for the mailbox folders (obviously different on Win and Linux, as the windows partition will be mounted under a certain directory in Linux, not the C:...) are in the separed config files.
Whith this schema there is no problem in reading configuration: the files are simply merged. The problem arises when you want to update it, as M must keep track of hte location of each directive, updating it in the original file. This way when you update the window position, M will write in the OS specific base configuration file, where it found the original window positions. When you add a filter M will write in the common include file, where it found the original filter list. This way the user can choose what configuration items keep common and which to keep independent.
Ciao
Stefano Salvi
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-users
