From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] some new features in SVN head
Date: Sun, 20 May 2007 16:55:56 -0700 [thread overview]
Message-ID: <1179704745-sup-2076@south> (raw)
1. When viewing attachments, if the external MIME command fails, Sup
will now display it inline as text. I have no idea what kind of
tragic things happen when you try to do this with a binary file.
Probably ncurses will burn a whole in your screen.
(As an aside, if anyone knows how to properly launch applications on
OS X by MIME type, please tell me.)
2. There's a new configuration option determining whether messages with
the same subject are grouped together in a thread, even if they don't
explicitly reference each other in the In-Reply-To or References
headers. This is useful if you get lots of mail from broken MUAs
which don't properly set those headers.
By default this is OFF. Previously it was ON and not configurable.
Turning if off speeds things up, because Sup will do additional
Ferret queries to find messages with the same subject that occur
in the recent past, which basically doubles the number of queries.
The upshot is that index loading should be faster next time you svn
update, until you explicitly turn this functionality back on.
3. I've added a batch deletion tool, bin/sup-sync-back, which will
delete (or move) messages from a source which are marked as deleted
or spam in the Sup index. This currently only works with mbox
sources.
Please be careful and make a backup before playing with this. It
works for me, but it's not thoroughly tested and is the first time
Sup has ever done anything destructive with your mail.
Currently you have to also run sup-sync --changed afterwards.
Comments, bug reports, etc. are welcome.
--
William <wmorgan-sup at masanjin.net>
reply other threads:[~2007-05-20 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1179704745-sup-2076@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