From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>
Cc: martin f krafft <madduck@madduck.net>, notmuch@notmuchmail.org
Subject: Re: inbox/unread tags for new messages [was: Re: Thoughts on notmuch and Lua]
Date: Sun, 17 Jan 2010 02:05:56 -0500 [thread overview]
Message-ID: <20100117070556.GA32233@finestructure.net> (raw)
In-Reply-To: <87pr59ihoy.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
On Sat, Jan 16, 2010 at 06:33:17PM -0800, Carl Worth wrote:
> I have thousands of messages that I have read with sup and notmuch. The
> filenames have never changed since the mail was originally delivered by
> maildrop. So these messages are all in "new" directories, do not have
> the 'S' flag in the filename, and do not have an "unread" tag.
>
> So the database and the filesystem are currently inconsistent and
> neither of the above state changes will trigger for any of these
> messages.
>
> Things "work" fine for me now because I'm treating the database state as
> authoritative and ignoring the names of the files. Your proposal is to
> treat the filenames as authoritative, so will require an additional
> step, (to copy the current state from the database to the file names),
> besides what you've outlineed above.
I guess my take on this is that notmuch is a mail processing program
with nominal support for maildir, and should therefore be following
the maildir specification. I wouldn't say this necessarily means that
the filesystem is "authoritative", just that the specification is
being followed. I could also see notmuch punting on that and just
offering something that indexes messages stored in individual,
uniquely named files.
I can definitely see, though, that switching to fully following the
maildir spec would require a bit more work and a transition. My
personal opinion is that notmuch should follow the maildir
specification. It would definitely facilitate interoperability with
other MTAs and MUAs that do properly follow the maildir specification.
jamie.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-01-17 7:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 8:47 Thoughts on notmuch and Lua Ali Polatel
2010-01-14 23:00 ` Carl Worth
2010-01-15 0:16 ` martin f krafft
2010-01-15 20:45 ` Carl Worth
2010-01-15 21:09 ` Ali Polatel
2010-01-15 23:15 ` Carl Worth
2010-01-16 19:10 ` Ali Polatel
2010-01-16 20:18 ` inbox/unread tags for new messages [was: Re: Thoughts on notmuch and Lua] Jameson Rollins
2010-01-16 22:22 ` Carl Worth
2010-01-16 23:38 ` Jameson Rollins
2010-01-17 2:05 ` Ben Gamari
2010-01-17 2:33 ` Carl Worth
2010-01-17 7:05 ` Jameson Rollins [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=20100117070556.GA32233@finestructure.net \
--to=jrollins@finestructure.net \
--cc=cworth@cworth.org \
--cc=madduck@madduck.net \
--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).