From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [PATCH] dont check thread-index-mode dirtiness on every keypress
Date: Sat, 23 Jan 2010 19:17:17 -0800 [thread overview]
Message-ID: <1264303037-17440-1-git-send-email-rlane@club.cc.cmu.edu> (raw)
Now that changes are instantly written to the index it's unnecessary to put the
"modified" message in the status line. Removing this cuts the time for a simple
action like moving the cursor by 75% or more, depending on the number of
messages loaded.
---
lib/sup/modes/thread-index-mode.rb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/sup/modes/thread-index-mode.rb b/lib/sup/modes/thread-index-mode.rb
index a6bb2b9..71c8f44 100644
--- a/lib/sup/modes/thread-index-mode.rb
+++ b/lib/sup/modes/thread-index-mode.rb
@@ -651,7 +651,7 @@ EOS
if (l = lines) == 0
"line 0 of 0"
else
- "line #{curpos + 1} of #{l} #{dirty? ? '*modified*' : ''}"
+ "line #{curpos + 1} of #{l}"
end
end
--
1.6.3.3
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-01-24 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 3:17 Rich Lane [this message]
2010-02-27 7:48 ` Rich Lane
2010-03-01 14:58 ` 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=1264303037-17440-1-git-send-email-rlane@club.cc.cmu.edu \
--to=rlane@club.cc.cmu.edu \
--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