On Wed, Jan 2, 2013 at 1:33 PM, Mark Alexander <ma...@pobox.com> wrote: > Excerpts from Jonathan Lassoff's message of Wed Jan 02 15:26:15 -0500 2013: >> I'm having a sad day with sup. I'm crashing with a Xapian error I'll >> have to dig into. > > I've never attempted to debug these kinds of crashes (which I run into > once or twice a year). Instead, I use sup-dump to save the state of > the index, rename .sup/xapian to .sup/xapian.bad, then use sup-sync > --restore to rebuild the index.
I started digging, but got bored with reading about the Xapian APIs, so I mostly did what you just did as well :P However, I needed to perform a sup-sync first to create the index and add the messages in, so when I restored from the dump, pretty much everything was marked as unread. Working in the console to declare inbox bankruptcy and inbox zero, and just clearing it all out. Thank goodness I'm starring threads that I need to follow up on! :p > Even though sup is not maintained, I'm so addicted to it that I'm willing > to put up with this inconvenience once in a while. Yeah, I've been using sup for so long that I can't just let it go now. I've got all these excellent hooks and I know the system well. Have you looked at Heliotrope / Turnisole yet? That totally seems like wmorgan's future mail architecture, and I've been curious to migrate to it, but haven't been able to sink the time into it just yet. Cheers, jof _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
