From: Gregor Hoffleit <gregor@hoffleit.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] Slow Sup: Drawing speed depends on window height?
Date: Mon, 19 Apr 2010 17:48:09 +0200 [thread overview]
Message-ID: <1271690970-sup-7143@sam.mediasupervision.de> (raw)
My Sup window is about 60 lines high. Interacting with Sup feels slow,
even simple actions like tagging/untagging threads ('t') in the Inbox.
Only recently I noticed that interaction speed is much better in a
smaller terminal window (in the sense of less lines, the width seems to
be no issue).
To reproduce: A simple benchmark is to tag the first 10 threads of the
page. In a terminal window with 60 lines, I type ten "t"'s and then can
wait for several seconds, watchin the cursor move down line be line.
In a terminal with 20 lines, the cursor moves almost the same speed as I
type.
FWIW, I'm running the next branch on a Debian lenny system, with
packages ruby1.8 (1.8.7.174-2), libncurses-ruby1.8 (1.2.3-0.2) etc.pp.
Regards,
Gregor
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2010-04-19 15:57 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=1271690970-sup-7143@sam.mediasupervision.de \
--to=gregor@hoffleit.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