Date: Sun, 17 Jan 2010 02:05:56 -0500
From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>
Message-ID: <20100117070556.GA32233@finestructure.net>
References: <20100114084713.GA22273@harikalardiyari>
	<87eilse1hg.fsf@yoom.home.cworth.org>
	<20100115001600.GD25209@lapse.rw.madduck.net>
	<87vdf3cd1y.fsf@yoom.home.cworth.org>
	<20100115210934.GA12515@harikalardiyari>
	<87r5prc64e.fsf@yoom.home.cworth.org>
	<20100116201803.GA19570@finestructure.net>
	<87bpgtd71q.fsf@yoom.home.cworth.org>
	<20100116233840.GA31869@finestructure.net>
	<87pr59ihoy.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp"
Content-Disposition: inline
In-Reply-To: <87pr59ihoy.fsf@yoom.home.cworth.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: martin f krafft <madduck@madduck.net>, notmuch@notmuchmail.org
Subject: Re: [notmuch] inbox/unread tags for new messages [was: Re: Thoughts
 on notmuch and Lua]
Precedence: list


--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> So the database and the filesystem are currently inconsistent and
> neither of the above state changes will trigger for any of these
> messages.
>=20
> 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.

--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: attachment

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLUrbRAAoJEO00zqvie6q80e8P/i8StL+Q0aBfUskr2SjRCgoX
R2jrW5cfu3eaG7ftZ1HFcZD0KNKpTf3KGr5BOn2jxR4ye93A+LEZn/vih+pbZKJn
FuoinI+fvGY9rInpB94h9VHikJGmbLK/S5T987pDLR3d2CmDhdsjn8bgov3wt4xd
zjnQh8BfBazyMC2kLzfPQu7pRNxTjvepGXpqi+Z8r2u+8q2INPC7QDPXbJCm1eXh
lsEADeNewGTyKWMaVTZa0KmVMw/EiRHoCoW999Lw6f5AuO4QcGTH64MKnhn2bmUC
bgWC+bbpPsMl7Px6mAAZA+gRlmZ1tpEo/qwRFzk8eSZkca9SWSwaEn59dPehfQX8
WcwIKEY8EYO7tceX1peZ5wXMNg/y4ym0GODxUrzV0E9BGi89ZGS1Zo3hvEtpzmkh
dqpT9ZzEUhXNc7HEKB44RvEPRsCs+EMt3xRR8H+wqbb7CHiWvVutYFJ6dKZyXF5S
fhGIQBmf7Mace+TlInjUseAdO/OqLHczai5ptb+iOtOsL51R3+xXuQvGVFBR1R7z
5VqvPk/FsG7eRkbhcx57Z87TpoAkMT2c6SV0vXn8bl4ldDgg0eZc/pk18Sjfegos
gf+t3kN7JtfwyeY+LALTsgEkEI+r3YLjC8cNUBAj3aUzU5ErnDy15ELXXVnGRAtf
a/ZyWNahg5rmrzCkM7+V
=Dvb5
-----END PGP SIGNATURE-----

--17pEHd4RhPHOinZp--