From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [Sup-announce] [ANN] Sup 0.9 released
Date: Thu, 01 Oct 2009 11:43:49 -0700 [thread overview]
Message-ID: <1254422532-sup-9948@masanjin.net> (raw)
I'm pleased to announce the release of Sup 0.9.
Sup is a console-based email client for people with a lot of email.
It supports tagging, very fast full-text search, automatic contact-
list management, and more. If you're the type of person who treats
email as an extension of your long-term memory, Sup is for you.
Get it: gem install sup
Learn it: http://sup.rubyforge.org
Love it: sup-talk at rubyforge.org
Excitement in 0.9:
* Experimental Xapian backend to replace Ferret. Not everything works with it,
but it's fast and less likely to barf. See release notes.
* New keybinding: "G" for reply-all.
* New hook: custom-search, for adding your own query expansions.
* Better preemptive thread loading.
* Random UI tweaks: display labels before subjects, change thread-view-mode's
'n' and 'p' commands slightly
* Better killing of other Sup processes.
* Die gracefully upon SIGKILL.
* Finally figure out the curses+ruby magic to make SIGWINCH (i.e. xterm
resizing) work correctly.
* Add a console mode (press ~) for interactively playing with the index.
* Finally figure out the curses magic to stop the weird keyboard behavior after
leaving the editor.
* Improved logging. Logging now supports SUP_LOG_LEVEL environment variable.
Set this to "debug" for verbiage.
* As always, many bugfixes and tweaks.
Release notes:
There's a new Xapian backend as an alternative to the Ferret one. It's still in
a beta stage. It's much faster and much less prone to the random crashes than
Ferret, but certain things don't work yet, most noticeably the unread message
counts in label-list-mode.
You can switch back and forth between both indexes without harm, *except* any
new messages added to the one index won't be picked up by the other. Follow
these instructions:
To TRY the Xapian index, without screwing Ferret up:
1. sup-dump > dump # takes a while
2. export SUP_INDEX=xapian # or however you do it in your shell
3. sup-sync --all --all-sources --restore dump # takes a long time
4. sup -n # -n ensures that no polling is done. don't hit 'P' either
Step 1 will take a long time, and step 3 will take a very long time.
At this point, whenever you run Sup, the SUP_INDEX environment variable will
determine which index you use. If it's unset, or "ferret", you will use the
ferret index. If it's "xapian", the Xapian index. Make sure when you run sup
with the Xapian index, you use -n and don't hit 'P', to avoid loading new
messages into it.
If you want to switch to Xapian permanently, you can then:
1. rm -rf ~/.sup/ferret
2. permanently set SUP_INDEX=xapian according to your shell
3. Run sup as normal, i.e. without -n.
If you want to go back to Ferret, you can just rm -rf ~/.sup/xapian and make
sure your SUP_INDEX environment variable is unset.
--
William <wmorgan-sup at masanjin.net>
reply other threads:[~2009-10-01 18:43 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=1254422532-sup-9948@masanjin.net \
--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