On Tue 14, Jul'09 at 11:14 AM -0400, Andrei Thorp wrote:
People perhaps don't want this. It's slower, and a lot of folks probably do no syncing back since all they use is sup anyway.
I would hope in this day in age we can change a database entry and move a file at the same time without too much of a performance hit. I would think it only gets unbearable when you don't update as you go and you have to do a large batch of messages. But you are right, maybe people don't want that.
Personally, and this is a side note, if I was involved in the project, I'd push for canning the built in IMAP capabilities all together. Just run offlineimap or one of the other IMAP syncing utilities. Add to that beefing up the Maildir handling. Just worry about better and more transparent sync-back-to-Maildir capabilities and let offlineimap worry about the server side of the equation.
Understood. Makes sense in your use case. I don't really understand why you'd want to use pine/mutt when you've already got sup though ;)
As you can tell, I'm not quite sold on sup yet. I've switched mail clients enough over the past few years that switching in and of itself is a giant pain. I've settled on Maildir as my 'client' for now. I can serve it via IMAP if I need, I can read it with a couple mail clients, and I can easily convert it to mbox however I want to with some simple Python code.
If I switch to sup full time, I would be comforted by the fact that if I choose to change in 2 years, all of my mail is marked read, deleted mail is actually deleted, and even though I was using sup labels for my organization, things are still organized in some fashion by appropriate folders on the file system. The last part could be achievable by some combination of offlineimap + gmail/sieve filtering and fetchmail/getmail + procmail. It'd still be nice to be able to move physical messages around in sup though. Maybe I'm just nuts though.
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
