I just tried.. im getting the same, afraid im not skilled enough to figure out what is wrong thou..
--- ArgumentError from thread: load threads for thread-index-mode invalid byte sequence in US-ASCII /home/gaute/dev/ruby/sup.git/lib/sup/util.rb:181:in `scan' /home/gaute/dev/ruby/sup.git/lib/sup/util.rb:181:in `display_length' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:224:in `block in draw_line_from_array' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:222:in `each' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:222:in `each_with_index' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:222:in `draw_line_from_array' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:197:in `draw_line' /home/gaute/dev/ruby/sup.git/lib/sup/modes/line-cursor-mode.rb:50:in `draw_line' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:48:in `block in draw' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:48:in `each' /home/gaute/dev/ruby/sup.git/lib/sup/modes/scroll-mode.rb:48:in `draw' /home/gaute/dev/ruby/sup.git/lib/sup/modes/line-cursor-mode.rb:37:in `draw' /home/gaute/dev/ruby/sup.git/lib/sup/buffer.rb:108:in `draw' /home/gaute/dev/ruby/sup.git/lib/sup/buffer.rb:92:in `redraw' /home/gaute/dev/ruby/sup.git/lib/sup/buffer.rb:329:in `draw_screen' /home/gaute/dev/ruby/sup.git/lib/sup/buffer.rb:744:in `clear' /home/gaute/dev/ruby/sup.git/lib/sup/util.rb:520:in `method_missing' /home/gaute/dev/ruby/sup.git/lib/sup/modes/thread-index-mode.rb:638:in `load_n_threads' (eval):12:in `load_n_threads' /home/gaute/dev/ruby/sup.git/lib/sup/modes/thread-index-mode.rb:609:in `block in load_n_threads_background' /home/gaute/dev/ruby/sup.git/lib/sup.rb:78:in `block in reporting_thread' - gaute On Sat, Nov 7, 2009 at 4:22 AM, Andrei Thorp <gar...@gmail.com> wrote: > Eh, bad news. > > So I've been testing Sup in an 1.9 environment further, and I have > found that there are a great deal of problems with regards to > encodings. "invalid byte sequence in US-ASCII" is something you'll see > frequently. This seems to be when parsing messages that have non-ascii > chararacters. > > Ouch :( > > Has this already been taken care of in the git somewhere? > > -AT > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk