Archive of RubyForge sup-announce mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk mailing list <sup-talk@rubyforge.org>,
	sup-announce mailing list <sup-announce@rubyforge.org>
Subject: [sup-talk] [ANN] Sup 0.9.1 released
Date: Fri, 11 Dec 2009 09:13:50 -0800	[thread overview]
Message-ID: <1260551530-sup-6131@masanjin.net> (raw)

I'm pleased to announce the release of Sup 0.9.1.

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@rubyforge.org

Release notes:

This is mainly a bugfix release, with a couple minor new features rolled up.

If you are using the Ferret backend, consider convering soon. I will probably
add a deprecation notice in 0.10, and you support will be dropped in 0.11.

Excitement in 0.9.1:

* Make textfield behave more like readline, including C-w
* Add ask_for_to config option. You can set all ask_for_* options to false, and
  composing a message will go immediately to the editor.
* RFC 2047 decode attachment file names
        * default ask_for_to to true
* add undo power to thread-view-mode
* display labels of polled messages
* increase numbers in contact-list-mode
* fix --compose option, and add a --subject option
* include hook filename in error messages
* As always, many bugfixes and tweaks.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


                 reply	other threads:[~2009-12-11 18:00 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=1260551530-sup-6131@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --cc=sup-announce@rubyforge.org \
    --cc=sup-talk@rubyforge.org \
    /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