From: John Wyzer <john.wyzer@gmx.de>
To: sup-devel Mailing List <sup-devel@rubyforge.org>
Subject: [sup-devel] [bug] trace: undefined method `mark_dirty' for nil:NilClass
Date: Sat, 12 Feb 2011 15:07:05 +0100 [thread overview]
Message-ID: <1297519607-sup-128@localhost> (raw)
Hi.
sup v0.12.1:
Submitting it here since the bugtracker is down.
I got this when I hit the "u" key after killing a thread.
--- NoMethodError from thread: main
undefined method `mark_dirty' for nil:NilClass
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/line-cursor-mode.rb:68:in `set_cursor_pos'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:240:in `update'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:717:in `add_or_unhide'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:479:in `block (2 levels) in multi_kill'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:477:in `each'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:477:in `block in multi_kill'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/undo.rb:27:in `call'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/undo.rb:27:in `block in undo'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/undo.rb:27:in `each'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/undo.rb:27:in `undo'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/modes/thread-index-mode.rb:227:in `undo'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/mode.rb:59:in `handle_input'
/var/lib/gems/1.9.1/gems/sup-0.12.1/lib/sup/buffer.rb:277:in `handle_input'
/var/lib/gems/1.9.1/gems/sup-0.12.1/bin/sup:260:in `<module:Redwood>'
/var/lib/gems/1.9.1/gems/sup-0.12.1/bin/sup:69:in `<top (required)>'
/var/lib/gems/1.9.1/bin/sup:19:in `load'
/var/lib/gems/1.9.1/bin/sup:19:in `<main>'
--
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2011-02-12 15:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1297519607-sup-128@localhost \
--to=john.wyzer@gmx.de \
--cc=sup-devel@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