Re: Database location bug when database does not already exist

Hello, On Sat 03 Sep 2022 at 08:34AM -03, David Bremner wrote: > Sean Whitton writes: > >> Hello, >> >> In the following situation: >> >> - only notmuch config is ~/.notmuch-config >> - database.mail_root is set >> - database.path is not set >> - notmuch database does not yet exist >> >> then no

Re: Database location bug when database does not already exist

Sean Whitton writes: > Hello, > > In the following situation: > > - only notmuch config is ~/.notmuch-config > - database.mail_root is set > - database.path is not set > - notmuch database does not yet exist > > then notmuch wants to create its db under mail_root/.notmuch, contrary > to notmuch-c

Re: Database location bug when database does not already exist

David Bremner writes: > Sean Whitton writes: > >> Hello, >> >> In the following situation: >> >> - only notmuch config is ~/.notmuch-config >> - database.mail_root is set >> - database.path is not set >> - notmuch database does not yet exist >> >> then notmuch wants to create its db under mail_r

Re: Database location bug when database does not already exist

Sean Whitton writes: > Hello, > > In the following situation: > > - only notmuch config is ~/.notmuch-config > - database.mail_root is set > - database.path is not set > - notmuch database does not yet exist > > then notmuch wants to create its db under mail_root/.notmuch, contrary > to notmuch-c

Database location bug when database does not already exist

Hello, In the following situation: - only notmuch config is ~/.notmuch-config - database.mail_root is set - database.path is not set - notmuch database does not yet exist then notmuch wants to create its db under mail_root/.notmuch, contrary to notmuch-config(1). -- Sean Whitton __