From: Stephen Paul Weber <singpolyma@singpolyma.net>
To: Michal Sojka <sojkam1@fel.cvut.cz>
Cc: notmuch@notmuchmail.org
Subject: Re: A problem and a suggestion
Date: Wed, 11 Aug 2010 13:31:37 -0500 [thread overview]
Message-ID: <20100811183137.GB1546@singpolyma-svelti> (raw)
In-Reply-To: <87d3ttfbym.fsf@steelpick.2x.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Somebody claiming to be Michal Sojka wrote:
> On Fri, 06 Aug 2010, Stephen Paul Weber wrote:
> > Anyway. I installed notmuch a few days ago (0.1), ran the setup, ran
> > notmuch new and i said it found 30000+ files, but no new mail? No searches
> > return any results. What am I doing wrong?
>
> I guess you have your mails in a wrong fomrat. Do you see "Note:
> Ignoring non-mail file" messages during notmuch new? You may also try
> notmuch new --verbose.
Hmm. I'm pointing it at a maildir. I deleted the .notmuch folder in the
maildir and ran notmuch new --verbose with the following result:
$ notmuch new --verbose
Found 33065 total files (that's not much mail).
No new mail.
and searches turn up no results.
> > I gather by other threads on the list archives that editing a message
> > does not make it "new"? So notmuch just gets whatever the first
> > version of the message contents it sees is? And if the file gets
> > renamed (by mutt for example, when marked as read) the filename stored
> > by notmuch would then be wrong?
>
> Yes. AFAIK notmuch assumes that messages are immutable and when you edit
> the message, notmuch doesn't re-index it.
Ok, so edited headers are ignored.
> Notmuch new code is able to
> detect renames so if you rename the file, the filename in the database
> is wrong only until you run notmuch new again.
Oh, cool. Good.
> > This would be especially useful if notmuch re-indexed a message when I
> > edit this header.
>
> I'm not sure how hard it would be to implement this and what would be
> the performance implications. You should store modification time of a
> message in the database and re-index the file when the mtime on disk in
> newer than in the database.
Right. An mtime-based solution would make sense to me. That should (I
would think) have minor performance implications unless you edit a lot of
your mail often.
- --
Stephen Paul Weber, @singpolyma
See <http://singpolyma.net> for how I prefer to be contacted
edition right joseph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMYuyJAAoJENEcKRHOUZzen1cP/0kgDgQQDR3nDn7mnw5t6Pfh
8IGODVtxSRJ+vFfrNg3gqUDHmHdphXAlX3xjvjI3eNLDW7PqmqUuQw4fzxQ6/cEQ
FBOlMq8zXze+Cus3baqYLIYltQaJRItsg4/5B4TjJXYC0r5W4Vt76wQNuBjAdDp5
EnEEpJEZypBlNyo6L33lsnkOQXnKPW/YPay5AT7FPYPIBv1BtyomJYAA6bUXEttD
BhcDoq+QZyOUKmShF9p1PtpAC7fKo2AtCALIK0CTClPWQidsLR/LYFxx1UaNvSjR
vG2S2H/FlyAzgYj+rgGoH/3rFLnSFjZE6rgpZsXnfQf2/KHnuzL0GSFcI0lsYlJR
Fyv/V7iPIYCkf0xG1deeoZ1Y0/qNidvzBwdJ9o6uaon/SINnvBegNksNhnaTS2Gb
B1J8/IHLfmOiswucz/s5lLkZL78/bJoyHRwRdARTwjHpP6ylMl+ZB7RUVILuNqc6
c0F52V3S7Jt3eyEPFM7kuFfXsoaQZSe1kwQLyaY+RjRaoLwiv90vdjpylJa0y9qC
NSu8ZTNI5rIhfZuAgDUOexWn2zwiqV6r+hJIsFe7KBjVhDS9N7TE4hekNVVOz40y
KDLgm9oves8H0q6ynI29uraw8nD7XJqu+O8YPwu88N0+Q96qHPPWff1iISTwKTON
uFXOonuUlLm/TBn+azEJ
=dX/y
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-08-11 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 17:04 A problem and a suggestion Stephen Paul Weber
2010-08-08 13:52 ` Michal Sojka
2010-08-11 18:31 ` Stephen Paul Weber [this message]
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=20100811183137.GB1546@singpolyma-svelti \
--to=singpolyma@singpolyma.net \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/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).