Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Mariano Mara <mariano.mara@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [ANN] Sup 0.10 released
Date: Sun, 24 Jan 2010 12:59:41 -0300	[thread overview]
Message-ID: <1264348412-sup-7571@kafka> (raw)
In-Reply-To: <1264344055-sup-3295@masanjin.net>

Excerpts from William Morgan's message of Sun Jan 24 11:44:50 -0300 2010:
> I'm pleased to announce the release of Sup 0.10. This version is
> frickin' awesome because not only do we have Ruby 1.9 support, the
> Xapian backend is now the default!  The next version will discard Ferret
> like a used rag.
> 
> 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:
> 
> The Xapian backend is now the default. Convert your old, crash-prone
> Ferret index to Xapian by running sup-convert-ferret-index.
> 
> Using a Ferret backend will produce a deprecation notice, and will not be
> supported in 0.11.

I just updated and love the startup announcement (you got me for a minute). 
However I couldn't find sup-convert-ferret-index
I updated with 
sudo gem update sup
and even did a full updatedb just in case I was not looking in the right
places. I must say sup-convert-ferret-index is not here. 
Did I miss something (it's Sunday here) or is the file really missing?

TIA for sup, you guys rock!
Mariano

> 
> Many thanks to Rich Lane for Xapian and Ruby 1.9 work.
> 
> Excitement in 0.10:
> 
> * Make Xapian backend the default, and add deprecation notice to Ferret indexes.
> * Now Ruby 1.9 compatible (Xapian backend only).
> * Changes are now saved automatically to the index. Pressing "$" now just
>   forces a flush of Xapian indexes, which can minimize quit time.
> * Fix problem with replying to Google Groups messages.
> * Allow toggling of line wrap. Useful for long URLs.
> * Multiple attachments can be added at once by specifying a wildcard.
> * New command to save all attachments at once.
> * As always, many bugfixes and tweaks.
> 
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-01-24 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 14:44 [sup-devel] " William Morgan
2010-01-24 15:59 ` Mariano Mara [this message]
2010-01-24 17:02   ` [sup-talk] " William Morgan
2010-01-24 17:30     ` William Morgan
2010-01-25  0:02       ` Mariano Mara
2010-01-25 20:14         ` William Morgan
2010-01-27  0:07 ` [sup-talk] [Sup-announce] " Decklin Foster
2010-01-27 13:51   ` William Morgan

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=1264348412-sup-7571@kafka \
    --to=mariano.mara@gmail.com \
    --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