Subject: [sup-talk] exception with undomanager

From: [email-masked] (Ben Walton)
Date: Sun, 07 Jun 2009 08:33:49 -0400

Hi All,

I bumped into this this morning.  I've not used the undo stuff much,
but I tried it today.  The (rough) sequence of events leading to this
was: I archived two threads separately and then decided I wanted to
undo the first of two actions.  I hit u once and got the latest thread
back and when I hit it again, sup crashed.  If I get a chance I'll
look into it myself, but I'm tossing it out for people more familiar
with these bits to see also.

Thanks
-Ben

$ less ~/.sup/exception-log.txt 
--- NoMethodError from thread: main
undefined method `content_width' for nil:NilClass
./sup/modes/thread-index-mode.rb:868:in `from_width'
./sup/modes/thread-index-mode.rb:793:in `text_for_thread_at'
/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`each_with_index'
./sup/modes/thread-index-mode.rb:792:in `each'
./sup/modes/thread-index-mode.rb:792:in `each_with_index'
./sup/modes/thread-index-mode.rb:792:in `text_for_thread_at'
./sup/modes/thread-index-mode.rb:753:in `regen_text'
./sup/util.rb:346:in `map_with_index'
/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`each_with_index'
./sup/util.rb:346:in `each'
./sup/util.rb:346:in `each_with_index'
./sup/util.rb:346:in `map_with_index'
./sup/modes/thread-index-mode.rb:753:in `regen_text'
./sup/modes/thread-index-mode.rb:228:in `update'
./sup/modes/thread-index-mode.rb:697:in `add_or_unhide'
./sup/modes/thread-index-mode.rb:319:in `actually_toggle_spammed'
./sup/undo.rb:28:in `call'
./sup/undo.rb:28:in `undo'
./sup/undo.rb:28:in `each'
./sup/undo.rb:28:in `undo'
./sup/util.rb:505:in `send'
./sup/util.rb:505:in `method_missing'
./sup/modes/thread-index-mode.rb:217:in `undo'
./sup/mode.rb:50:in `send'
./sup/mode.rb:50:in `handle_input'
./sup/buffer.rb:249:in `handle_input'
../bin/sup:237
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090607/3fcc2660/attachment.bin>

---

From: [email-masked] (William Morgan)
Date: Mon, 08 Jun 2009 10:18:30 -0700

> with these bits to see also.

Something like this seems to happen fairly frequently. I think it's a
(shudder) threading issue. Something is killing a buffer (possibly the
user) while it's being redrawn and this happens. I need to stick another
mutex in there somewhere. Or rewrite Sup for Ruby 1.9 with fibers
instead of threads.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Edward Z. Yang)
Date: Mon, 08 Jun 2009 14:18:41 -0400

> mutex in there somewhere. Or rewrite Sup for Ruby 1.9 with fibers

The unfortunate bit about Ruby 1.9 is that the majority of libraries sup uses
aren't on 1.9 yet...

Cheers,
Edward

---

From: [email-masked] (Ben Walton)
Date: Mon, 08 Jun 2009 14:50:19 -0400

> The unfortunate bit about Ruby 1.9 is that the majority of libraries sup uses

...and some platforms don't have packages for it yet, which puts more
onus on the user to get it up and going...

-Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090608/836af547/attachment.bin>

---

From: [email-masked] (William Morgan)
Date: Mon, 08 Jun 2009 11:59:04 -0700

Reformatted excerpts from Edward Z. Yang's message of 2009-06-08:
> The unfortunate bit about Ruby 1.9 is that the majority of libraries
> sup uses aren't on 1.9 yet...

Not a serious suggestion. One rewrite going at a time is my rule. :)
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Edward Z. Yang)
Date: Mon, 08 Jun 2009 15:02:28 -0400

> onus on the user to get it up and going...

Ruby is basically not usable with your package manager. You *have* to
roll the gems yourself.

Cheers,
Edward

---

From: [email-masked] (Ben Walton)
Date: Mon, 08 Jun 2009 15:20:31 -0400

> Ruby is basically not usable with your package manager. You *have* to

I realize this.  Gems are awesome and gems suck.  I'm talking about
the matz ruby interpreter itself.  In some instances, not only would
the user need all of the gems, but they'd need a 1.9 ruby too...that a
big commitment to run a mail client.

[As a side note, Debian/Ubuntu do package many of the gems, but it's a
round hole, square peg affair.]

Thanks
-Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090608/33159422/attachment.bin>