From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-announce <sup-announce@rubyforge.org>,
sup-talk <sup-talk@rubyforge.org>,
sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] Sup 0.12.1 released
Date: Mon, 24 Jan 2011 01:05:04 -0500 [thread overview]
Message-ID: <1295848539-sup-752@zyrg.net> (raw)
I'm pleased to announce the release of Sup 0.12.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 release changes the gem dependency on ncurses to ncursesw, which
allows the gem to install cleanly on Ruby 1.9.
The new sup-import-dump program applies labels to an existing index,
which could be done with sup-sync before 0.12.
Changelog for 0.12.1:
* Depend on ncursesw rather than ncurses (Ruby 1.9 compatibility)
* Add sup-import-dump
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2011-01-24 6:23 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=1295848539-sup-752@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=sup-announce@rubyforge.org \
--cc=sup-devel@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