From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Mon, 29 Oct 2007 08:46:31 -0700 Subject: [sup-talk] sup-sync-back: killed threads and read status In-Reply-To: <6205b42d0710142302u2ca4c6c0yc53336434bc4fe39@mail.gmail.com> References: <6205b42d0710142302u2ca4c6c0yc53336434bc4fe39@mail.gmail.com> Message-ID: <1193672440-sup-8648@south> Excerpts from Pierre Baillet's message of Sun Oct 14 23:02:12 -0700 2007: > sup-sync-back does not seem to delete killed messages. I think, it > should do that. It shouldn't delete them. A killed thread is a thread you don't want to ever show up in the inbox, but that's not the same as wanting to delete something. You may want to keep that thread around for later browsing or searching. GMail used to call them murdered threads, but changed the name to muted threads in the release. Maybe I should call them "kept quiet" threads. :) > Moreover, the "Read" status of emails is not changed in the original > mailbox. I'm not sure it's sup-sync-back job to do that, but the > Principle Of Least Surprise would probably expect that. I've purposely avoided writing changes back to the original sources, since it's a world of pain, will never be 100% complete (Sup state is much more complex than Maildir/IMAP/mbox state), and doesn't fit in the Sup weltanshaung of treating sources as dumb buckets. I will accept patches to sup-sync-back to set read/unread status, but only grudgingly! -- William