Hi Arvid, Sorry to hear about your negative experience. Sounds like it's several unrelated issues all adding up.
Reformatted excerpts from Arvid Picciani's message of 2010-01-14: > The interface only responds to shift-q. Typing only "q" will prompt and > that prompt can not be answered with y Y ^y sane for the ^C prompt. Sounds like you're using Ruby 1.9. You can either use Ruby 1.8, sup next (bleeding-edge code, as you see below), or wait for Sup 0.10. > So i went to the git next tree: It takes 30 seconds to start on a > core2, and uses 100% cpu polling for new messages apparantly. Screen > is flooded with ruby warnings, so it is unusable. Can you run sup-sync before running Sup the first time? Adding new messages does take a lot of CPU, but it's typically only an issue if you have to add lots of documents. > /home/aep/kram/mainline/lib/sup/xapian_index.rb:52:in `save_index': > undefined method `flush' for nil:NilClass (NoMethodError) Fixed in next already. Sorry about that. > --- NoMethodError from thread: poll after loading inbox > undefined method `[]' for nil:NilClass > /home/aep/kram/mainline/lib/sup/xapian_index.rb:570:in `mkterm' > /home/aep/kram/mainline/lib/sup/xapian_index.rb:345:in `find_docid' I believe this is also fixed in next. Please try again. -- William <[email protected]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
