Re: notmuchsync: handling of the deleted tag

[Sebastian Spaeth <Sebastian@SSpaeth.de>]

[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]

On Fri, 12 Nov 2010 13:16:53 -0800, Carl Worth wrote:
> [*] This is a point I'm not clear on. Would a tool like offlineimap be
> able to push custom filenames through to the remote end with standard
> imap servers?

Not sure. If it worked this would be really nice. But as most IMAP
server support arbitrary flags to be added to a message, I would still
think the best is to code a tool that talks IMAP and synchronizes
notmuch tags with the IMAP server. I've never done it before and
python's IMAP support is pretty crappy or I would alredy have given it a
go :).

> So questions of syntax aside, I'm not convinced that this idea is
> insane. And if it covers all of the synchronization needs that people
> really have.

Yes, it would cover a lot of my needs too. Altough I am still aiming at
propagating my notmuch flags via the IMAP server and back :).

> That's actually a question I wanted to ask you. If notmuch 0.5 actually
> does everything that notmuchsync did, then that's great news. If there
> is any missing functionality, then let's get that into notmuch.

Pruning used to be done nicely with notmuchsync, but you have given a
nice example how that could be done with notmuch now.

The one thing I can see now that notmuchsync still does is moving
maessages to a folder when they match a tag. But that would be an
equally short shell script that notmuch can do now. So, while I might
still fix bugs, I do not think that notmuchsync will evolve a lot
further (until I make it speak IMAP which I don't see coming in the near
future)

Sebastian

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]