On Fri 24 Dec 2021 at 09:03 -0400, David Bremner wrote: > > @Floris: when I made the change to the Database constructor, I chose the > default as CONFIG.NONE because this matched the previous semantics > _except_ for finding the database path. But since I don't want to use > the ad hoc default_path method anymore, maybe a better default would be > CONFIG.SEARCH. I guess most users of the python bindings will be OK with > the the configuration values in .notmuch-config being loaded by default. > What do you think?
Originally my intention with opening the database was that doing the same as notmuch itself does by default would be the default and most natural thing to do (whether or not I succeeded at the time I have no idea). So reading .notmuch-config by default and using it correctly seems fine to me. Backwards compatibility is always tricky I guess, but following notmuch's behaviour itself seems reasonable to me. As a random data point I just checked my own use and I seem to be passing the database path explicitly. Cheers, Floris _______________________________________________ notmuch mailing list -- email@example.com To unsubscribe send an email to notmuch-le...@notmuchmail.org