Re: [sup-talk] current state of synching upstream?

From: Rich Lane <rlane@club.cc.cmu.edu>
To: Ryan Barrett <sup-talk@ryanb.org>
Cc: sup-talk <sup-talk@rubyforge.org>, sjh <sjh@foolishpride.org>
Subject: Re: [sup-talk] current state of synching upstream?
Date: Sun, 11 Apr 2010 20:57:42 -0400	[thread overview]
Message-ID: <1271023429-sup-9851@zyrg.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1004080235530.8539@snarfed.org>

Excerpts from Ryan Barrett's message of 2010-04-08 05:40:32 -0400:
> hi all! i've been looking forward to trying sup since i first heard about it a 
> couple years ago, and i'm getting pretty close. one of my few remaining 
> concerns is using sup in parallel with other mail clients, including sup 
> itself.

My primary goal for the 0.12 release is making Sup play nice with other
clients. You can see the work in progress on the maildir branch - it's
getting more stable but it's still rough around the edges. Most of the
changes on this branch are to make Sup gracefully handle cases where
another client has moved or deleted mail out from under us.

Sup will automatically detect changes to the Seen flag in the maildir
and update the message's labels. I haven't decided what to do about the
other direction. Historically Sup has never modified mail sources, but
changing flags in a maildir is safe enough that I might implement it.
Running sup-sync-back has the problem that you can't run the UI at the
same time.

Does anyone use the current sup-sync-back that only support mboxes? If
there are no strong objections then the 0.12 sup-sync-back will only
support maildir.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk