Excerpts from William Morgan's message of Wed Aug 05 16:03:09 -0400 2009:

> Good point. I've fixed that in branch ncurses-fixes, which I've merged
> into next. Let me know if it works for you.

I just pulled next and fired it up.  It was _hoooooribly_,
_bruuuutallly_ slow to load the index.  I git bisected between my
previous running ORIG_HEAD and HEAD.  I came up with 75d9f5e3db as the
offender.  It seems to do what you intend but (for me, anyway) at the
expense of really bad interactivity.  [We're talking 10+ minutes to
load the index part way...]

This doesn't help identify the problem, but I'd be looking at the
Ncurses.nodelay bits...

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.

Attachment: signature.asc
Description: PGP signature

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

Reply via email to