From: Carl Worth <cworth@cworth.org>
To: Michal Sojka <sojkam1@fel.cvut.cz>, Dirk Hohndel <hohndel@infradead.org>,
	Matt Fleming <matt@console-pimps.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/4] Maildir synchronization
In-Reply-To: <87typbzdnt.fsf@steelpick.2x.cz>
References: <1273580061-22580-1-git-send-email-sojkam1@fel.cvut.cz>
	<87d3w082dh.fsf@linux-g6p1.site> <m3zkz3d210.fsf@x201s.gr8dns.org>
	<87typbzdnt.fsf@steelpick.2x.cz>
User-Agent: Notmuch/0.3.1 (http://notmuchmail.org) Emacs/23.2.1
	(i486-pc-linux-gnu)
Date: Fri, 29 Oct 2010 17:13:09 -0700
Message-ID: <87sjzopmga.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Thu, 10 Jun 2010 06:59:02 +0200, Michal Sojka <sojkam1@fel.cvut.cz> wrot=
e:
> This is a known limitation.
> From id:1273580061-22580-3-git-send-email-sojkam1@fel.cvut.cz:
>=20
>    The reason is that when you view the message its unread tag is
>    removed which leads to rename of the file, but Emacs still uses the
>    original name to access the attachment.
>=20
>    Workaround: close the message and open it again.

Hi Michal,

These patches do indeed look very interesting. But the above limitation
is really too severe. It just breaks things to much. Let's get that
fixed first.

> IMHO, the final solution to this issue would be the "notmuch cat"
> command. With this command, emacs would not access the messages by file
> name, but by message id.

Sounds like a great idea. Instead of "notmuch cat", how about we name
this "notmuch show --format=3Draw"? That should be even easier to
implement, too.

Then, I think I'll be very interested in the maildir-synchronization
patches, and further I'd like to have these enabled by default. After,
all the #1 item in the TODO list for quite some time has been:

1. A new import is tagging all messages as "inbox" -- total pain

And this has the potential to finally fix that.

Finally, as for configuration, I don't like the numeric codes for this
feature. Do we really need that much granularity in the functionality
here? Other mail clients certainly don't. From what I can see, most mail
clients just twiddle these flags unconditionally.

I can imagine some people might want to be able to turn the feature off
entirely, so maybe we'll need that.

Or perhaps more importantly than configuration, we need the ability to
easily migrate people to a synchronized state. For example, in my
current mail store, most filenames have never been changed, so I've got
a lot of files with flags that don't match my tags. What do you think
would be the best way to resolve a situation like that?

Looking forward to more here,

=2DCarl

=2D-=20
carl.d.worth@intel.com

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFMy2MV6JDdNq8qSWgRAm2AAKCXOUw2I3RMVasO3tOSDVQ3WWpzdgCfQgIg
FPC4kD0wn0CmzTNp2EuQ0gs=
=kx0C
-----END PGP SIGNATURE-----
--=-=-=--