Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
* [sup-talk] two crashes on reply
@ 2007-11-12  0:48 Alec Berryman
  2007-11-12 18:23 ` William Morgan
  0 siblings, 1 reply; 5+ messages in thread
From: Alec Berryman @ 2007-11-12  0:48 UTC (permalink / raw)


I'm new to sup and running it from svn (r689), and get not one but two
crashes while trying to reply.

I sent a message to myself, then tried to reply to it by hitting 'r'
from the message list buffer I get when I start up.  It popped up a
buffer entitled "Customized reply" with the From line highlighted.  All
the fields - From, To, Cc, Bcc, Subject - were blank.  From here I can
trigger two crashes.

First, if I press enter, my editor pops up.  If I change the file's
contents, save, and exit, I get the following:

[Sun Nov 11 19:33:29 -0500 2007] locking /home/alec/.sup/lock...
[Sun Nov 11 19:33:29 -0500 2007] loading index...
[Sun Nov 11 19:33:29 -0500 2007] loaded index of 829 messages
[Sun Nov 11 19:33:29 -0500 2007] starting curses
[Sun Nov 11 19:35:47 -0500 2007] stopped cursing
[Sun Nov 11 19:35:47 -0500 2007] oh crap, an exception
[Sun Nov 11 19:35:47 -0500 2007] unlocking /home/alec/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup.
Please accept my sincere apologies. If you don't mind, please
send the backtrace below and a brief report of the circumstances
to sup-talk at rubyforge dot orgs so that I might address this
problem. Thank you!

Sincerely,
William
----------------------------------------------------------------

The problem was: 'undefined method `size' for nil:NilClass' (error type NoMethodError)
A backtrace follows:
./lib/sup/modes/reply-mode.rb:113:in `handle_new_text': undefined method `size' for nil:NilClass (NoMethodError)
    from ./lib/sup/modes/edit-message-mode.rb:94:in `edit_message'
    from ./lib/sup/mode.rb:54:in `send'
    from ./lib/sup/mode.rb:54:in `handle_input'
    from ./lib/sup/buffer.rb:203:in `handle_input'
    from bin/sup:210

If I don't change the contents, everything's fine.

The second crash comes if I try and use the reply-mode keybindings to
change the To field by pressing 't'.  I get this:

[Sun Nov 11 19:43:36 -0500 2007] starting curses
[Sun Nov 11 19:45:07 -0500 2007] stopped cursing
[Sun Nov 11 19:45:07 -0500 2007] oh crap, an exception
[Sun Nov 11 19:45:07 -0500 2007] unlocking /home/alec/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup.
Please accept my sincere apologies. If you don't mind, please
send the backtrace below and a brief report of the circumstances
to sup-talk at rubyforge dot orgs so that I might address this
problem. Thank you!

Sincerely,
William
----------------------------------------------------------------

The problem was: 'undefined method `join' for nil:NilClass' (error type NoMethodError)
A backtrace follows:
./lib/sup/modes/edit-message-mode.rb:306:in `edit_field': undefined method `join' for nil:NilClass (NoMethodError)
    from ./lib/sup/modes/reply-mode.rb:125:in `edit_field'
    from ./lib/sup/modes/edit-message-mode.rb:73:in `edit_to'
    from ./lib/sup/mode.rb:54:in `send'
    from ./lib/sup/mode.rb:54:in `handle_input'
    from ./lib/sup/buffer.rb:203:in `handle_input'
    from bin/sup:210

I get similar errors if I try to change CC:, but not if I try to change
the subject.

I'm also not sure why sup isn't filling in the To and Subject fields.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-11-14 13:12 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-12  0:48 [sup-talk] two crashes on reply Alec Berryman
2007-11-12 18:23 ` William Morgan
2007-11-13  0:16   ` Alec Berryman
2007-11-14  7:36     ` William Morgan
2007-11-14 13:12       ` Alec Berryman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox