Excerpts from William Morgan's message of Sat Sep 26 10:31:56 -0400 2009: > Sorry it's taken me so long to get back to this.
Quite alright. I know we're all busy. > > I definitely am not sure why there's a deadlock happening, but I am > guessing, based on the line numbers in that first exception, that it's > being triggered by an underlying problem with the source. If you run > sup with -n, does that change anything? (Or produce a better exception?) Well, things definitely failed a bit differently. I tried this a few times and after seeing no real improvement, I moved on to your suggestion below. > > > Anyways, this is the current status of things on my machine. William, do > > you have any ideas what might cause such a backtrace. At this point > > classes have started and I really have no more time to devote to > > getting sup working. If there isn't a fairly simple solution here I guess > > I'll just need to stick with mutt (ugh). Anyways, thanks for your work. > > Well, there's a workaround, which is to switch over to an offlineimap > setup where your Gmail is mirrored locally and Sup reads the mirror > (which is what you want anyways if you're serious about using Sup with > an IMAP client). I don't know what's causing the deadlock, but I will > try and reproduce it on my end. This is definitely what I should have done from the beginning. Given that sup seems to work fine after removing my imap sources, it seems that that might be the source of the above deadlock. I think I'll just stick with offlineimap for now. This does raise one important question, however. It seems that offlineimap will delete messages if they are found to have been deleted in the remote respository. Is there any way that you know of to disable this behavior, such that it will only drop new messages into the local repository, thus making it somewhat compatible with sup's add-only source requirement? It is awfully nice to be able to use GMail's web interface when I'm away from my computer, but needing to re-sync sup afterwards becomes quite tiresome. This actually brings up a larger question. How difficult would it be to relax sup's assumption that sources are add-only? This seems like a horribly restriction to have in an email program. I understand that in the case of sources such as imap where there is no globally unique message identifier trying to track message changes could be quite difficult, but for local sources (especially maildirs) it seems like this should be quite possible. Anyways, thanks a ton for your work. Now since I finally have sup up and running reliably, it's been a joy to use. Leaps and bounds above my former mutt-based system. - Ben _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
