From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] whistlepig
Date: Wed, 09 Feb 2011 06:14:52 +0000 [thread overview]
Message-ID: <1297231668-sup-8433@masanjin.net> (raw)
Today I've released something that I've been working on for many many months
now, which I hope will form the basis of the mythical Sup 2.0. It's a tiny
full-text search engine called Whistlepig.
http://masanjin.net/whistlepig
For a quick demo, if you clone it and check out the ruby/ directory, you can run:
ruby -Ilib bin/email-indexer <mbox name>
ruby -Ilib bin/email-searcher <mbox name>
(You will also need to install the oklahoma_mixer, console and trollop gems.)
This is a super simple non-threaded non-curses email browser. The email parsing
code is much of the Sup email parsing code, but I think I've ironed out all the
Ruby 1.9 encoding-related bugs through a very laborious process of trial and
error.
For my next trick, I am going to start writing a server version of this.
Believe it or not, I'm thinking HTTP.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2011-02-09 6: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=1297231668-sup-8433@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@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