Daniel Kahn Gillmor <[email protected]> writes: > > Sure, that sounds plausible, though i'd love to keep everything in a > single database without having to worry about a config file getting > de-synchronized from the database. >
I guess both of you know this already, but for the record notmuch can handle defined config items being in either the database or a config file. I guess you'd probably want to store just one config item with all of the mappings; it isn't clear what the keys would be otherwise. You can also read e.g. all keys with a certain prefix, so it might make sense to configure petname.dkg: [email protected] petname.mjg: [email protected] There are many possible variations, you probably know best what you want/need. I just wanted to mention the library support for config management. d _______________________________________________ notmuch mailing list -- [email protected] To unsubscribe send an email to [email protected]
