From: Eric Sherman <hyperbolist@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] [PATCH] [issue44] cursor sticks to thread
Date: Tue, 12 Jan 2010 15:12:04 -0500 [thread overview]
Message-ID: <1263327054-sup-3431@changeling.local> (raw)
The cursor will track the thread it is on when that thread is moved up
or down on the screen as threads are added or removed from the view.
---
lib/sup/modes/thread-index-mode.rb | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/lib/sup/modes/thread-index-mode.rb b/lib/sup/modes/thread-index-mode.rb
index a5bd344..9e70ec8 100644
--- a/lib/sup/modes/thread-index-mode.rb
+++ b/lib/sup/modes/thread-index-mode.rb
@@ -219,6 +219,10 @@ EOS
end
def update
+ ## remember the thread we are on and where the cursor is before we update
+ old_cursor_thread = cursor_thread
+ old_cursor_position = curpos
+
@mutex.synchronize do
## let's see you do THIS in python
@threads = @ts.threads.select { |t| !@hidden_threads[t] }.sort_by { |t| [t.date, t.first.id] }.reverse
@@ -226,6 +230,11 @@ EOS
@size_widget_width = @size_widgets.max_of { |w| w.display_length }
end
+ ## if the thread moved on screen, move the cursor to its new position
+ new_cursor_position = @threads.index(old_cursor_thread)||0
+ (old_cursor_position..(new_cursor_position-1)).each { |x| cursor_down }
+ (new_cursor_position..(old_cursor_position-1)).each { |x| cursor_up }
+
regen_text
end
--
1.6.6
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2010-01-12 20:12 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=1263327054-sup-3431@changeling.local \
--to=hyperbolist@gmail.com \
--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