From: Ico <sup@zevv.nl>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Sup crash
Date: Thu, 05 Jul 2012 21:19:50 +0200 [thread overview]
Message-ID: <1341515924-sup-8847@pruts.nl> (raw)
Hi,
Sup crashes on me when returning from the editor during a reply. Running the
latest version from git:
----------------------------------------------------------------
--- TypeError from thread: main
no implicit conversion from nil to integer
./lib/sup/horizontal-selector.rb:18:in `[]'
./lib/sup/horizontal-selector.rb:18:in `val'
./lib/sup/modes/edit-message-mode.rb:351:in `update'
./lib/sup/modes/reply-mode.rb:203:in `handle_new_text'
./lib/sup/modes/edit-message-mode.rb:213:in `edit_message'
./lib/sup/mode.rb:59:in `send'
./lib/sup/mode.rb:59:in `handle_input'
./lib/sup/buffer.rb:278:in `handle_input'
bin/sup:271
--
:wq
^X^Cy^K^X^C^C^C^C
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2012-07-05 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 19:19 Ico [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-24 8:12 [sup-talk] sup crash Lorenzo Bolla
2010-05-25 19:03 ` Anthony Martinez
2009-08-22 14:49 Carlos Franke
2009-08-22 16:31 ` William Morgan
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=1341515924-sup-8847@pruts.nl \
--to=sup@zevv.nl \
--cc=sup-talk@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