From: Michael Hamann <michael@content-space.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] now in next: fix-utf8, ferret-removal, and remote-source-deprecation
Date: Sun, 28 Feb 2010 22:58:25 +0100 [thread overview]
Message-ID: <1267393803-sup-784@mithink> (raw)
In-Reply-To: <1267389645-sup-7736@zyrg.net>
Hi,
thanks for your work, it seems I am able to send messages with UTF-8 subjects,
recipients, ... again, but after pulling from next I first had to do the
following fixes in order to get sup working again (I don't know if there are
more, these are just the two ones that made sup unusable):
diff --git a/lib/sup/index.rb b/lib/sup/index.rb
index 548daf0..79bd1af 100644
--- a/lib/sup/index.rb
+++ b/lib/sup/index.rb
@@ -216,10 +216,10 @@ EOS
## Given an array of email addresses, return an array of Person objects that
## have sent mail to or received mail from any of the given addresses.
- def load_contacts email_addresses, h={}
+ def load_contacts email_addresses, opts={}
contacts = Set.new
num = opts[:num] || 20
- each_id_by_date :participants => emails do |id,b|
+ each_id_by_date :participants => email_addresses do |id,b|
break if contacts.size >= num
m = b.call
([m.from]+m.to+m.cc+m.bcc).compact.each { |p| contacts << [p.name, p.email] }
@@ -739,14 +739,14 @@ class Xapian::Document
def index_text text, prefix, weight=1
term_generator = Xapian::TermGenerator.new
- term_generator.stemmer = Xapian::Stem.new(Redwood::XapianIndex::STEM_LANGUAGE)
+ term_generator.stemmer = Xapian::Stem.new(Redwood::Index::STEM_LANGUAGE)
term_generator.document = self
term_generator.index_text text, weight, prefix
end
alias old_add_term add_term
def add_term term
- if term.length <= Redwood::XapianIndex::MAX_TERM_LENGTH
+ if term.length <= Redwood::Index::MAX_TERM_LENGTH
old_add_term term, 0
else
warn "dropping excessively long term #{term}"
Greetings
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-02-28 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 21:20 Rich Lane
2010-02-28 21:58 ` Michael Hamann [this message]
2010-02-28 23:36 ` Rich Lane
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=1267393803-sup-784@mithink \
--to=michael@content-space.de \
--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