From: David Bremner <david@tethera.net>
To: Jack Kamm <jackkamm@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Breakage after updating to 0.32 (database and path issues)
Date: Mon, 10 May 2021 07:50:04 -0300 [thread overview]
Message-ID: <875yzqkgmb.fsf@tethera.net> (raw)
In-Reply-To: <87eeefdc8b.fsf@gmail.com>
Jack Kamm <jackkamm@gmail.com> writes:
> Update: I was able to fix my problems by explicitly setting "database.path" to "$HOME/mail" in my .notmuch-config. Then, notmuch was able to find my emails in my "$HOME/mail" as well as my database at "$HOME/mail/.notmuch".
>
> Confusingly, if "database.path" wasn't explicitly set in
> .notmuch-config, then "notmuch config get database.path" still
> returned "$HOME/mail", but notmuch cant' find the database, instead
> looking in ".local/share/notmuch/default". Is this a bug?
It's a bit surprising that you can't reproduce this anymore, because I
think there really was a bug here. I have sent a patch as a followup,
> Also, it seems like a bug that notmuch was unable to find any of my
>email when I had previously set "database.path" to
>"$HOME/mail/.notmuch". It seems like it was looking for the mail in
>"database.path" when it should have been looking in
>"database.mail_root".
Notmuch has to go through some contortions to support both nested
(.notmuch inside mail dir) and split configurations, and we may just
have to call this one unsupported. It didn't work before, so there is no
loss of functionality here.
> Finally, the manpage of notmuch-config(1) seems to be incorrect when
> it says that database.path will use a ".notmuch" subdirectory when
> "database.mail_root" is unset. In particular, "notmuch config get
> database.mail_root" returns "$HOME/mail", however "database.path" is
> still using a ".notmuch" subdirectory.
Sorry, I don't follow this. I don't _think_ there's an actual error
here, but if someone wants to propose patches that
make that part of the documentation clearer, I'd be happy to take a look
at them (although probably not for the point release, which I want to
get out the door).
next prev parent reply other threads:[~2021-05-10 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 14:58 Breakage after updating to 0.32 (database and path issues) Jack Kamm
2021-05-09 17:51 ` David Bremner
2021-05-09 18:08 ` Jack Kamm
2021-05-09 17:54 ` Jack Kamm
2021-05-09 18:52 ` Jack Kamm
2021-05-10 10:39 ` [PATCH] lib/open: restore default database path of $HOME/mail David Bremner
2021-05-15 12:12 ` David Bremner
2021-05-10 10:50 ` David Bremner [this message]
2021-05-16 23:50 ` Breakage after updating to 0.32 (database and path issues) Jack Kamm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yzqkgmb.fsf@tethera.net \
--to=david@tethera.net \
--cc=jackkamm@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).