Excerpts from Tim Gray's message of Tue Jul 14 09:45:44 -0400 2009: > On Tue 14, Jul'09 at 9:24 AM -0400, Andrei Thorp wrote: > > > a) It doesn't import them as read > > b) sup-sync-back does not mark them as read.
I'm forwarding a summary of your message with my replies to the mailing list. It seems like you replied to me only by accident? > From my playing around with sup and from what I've read, sup just doesn't > play nicely with other mail clients. Sup will read from your sources, but > the sources never get modified. Again, see sup-sync-back -- it does indeed have _some_ ability to write its state back to the source. > I know sup is slowly moving in the direction of a more locked in design. I > just wish sup added automatic sync back capabilities. Put this in a hook and it's automatic. That's the beauty of the hook/multiple binary design. > As far as OfflineIMAP goes, I didn't think I would do this, but I've been > running it in it's full curses mode with an auto refresh set. I'm not entirely sure why you want this. If you're worried about failures, do they really happen? If you want to see the log, aren't you already piping it? If you want notifications, you could hook them up to happen in your sup hook (the one I described before) rather trivially via notify-send. -- Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com) _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
