From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup-sync-back: killed threads and read status
Date: Mon, 29 Oct 2007 08:46:31 -0700 [thread overview]
Message-ID: <1193672440-sup-8648@south> (raw)
In-Reply-To: <6205b42d0710142302u2ca4c6c0yc53336434bc4fe39@mail.gmail.com>
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 <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-10-29 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 6:02 Pierre Baillet
2007-10-15 6:42 ` Christopher Warrington
2007-10-29 15:46 ` William Morgan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1193672440-sup-8648@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox