Package: mrxvt
Version: 0.5.2-2
Severity: normal

The mrxvt-0.5.2 source has a debugging constant defined that causes a very noticeable slowdown, especially over a remote connection or when the scrollback buffer gets large. I have waited awhile to report this because I was expecting an 0.5.3 release (as hinted at in the following message), but since this has not happened, I am still using a custom-compiled mrxvt to get around this problem. It's a simple one-line fix, so it would be nice to get this patch applied.

Thanks!
Dave

The following message is originally from the SourceForge forum, and can be found at:

http://www.nabble.com/-Fixed--Slowdown-in-mrxvt-0.5.2-p6829320.html

--snip--

[Fixed] Slowdown in mrxvt-0.5.2 Click to flag this post
by Gautam Iyer-2 Oct 15, 2006; 11:51pm

Hi All,

I fixed the bugs reported by Roy Lanek and Garry Zhang. Both of them
reported that mrxvt-0.5.2 was a little slower redrawing the screen in
some situations.

The problem was a brain malfunction on my part. When coding, I had
enabled DEBUG_X in revision 168, and *forgotten* to turn this off! This
caused mrxvt to request synchronous processing of X events, and thus a
tremendous slowdown!

Attached is a patch that fixes this (alternately, use the version from
subversion).

I also noticed that some shared files from the subversion tree (terminfo
+ documentation) were missing in the released 0.5.2. Thus if Garry and
Roy both report the problem fixed, I will nuke the 0.5.2 release, and
re-release as 0.5.3. [And thanks to both of you for pointing it out. God
knows how long it might have gone unnoticed otherwise].

Let me know,

GI

--
Alternative definitions of terms from Math Lectures:
PROOF OMITTED: Trust me, It's true.

Index: src/init.c
===================================================================
--- src/init.c (revision 195)
+++ src/init.c (working copy)
@@ -41,7 +41,7 @@
 # define DEBUG_X
 #else
 # define DEBUG_LEVEL 0
-# define DEBUG_X
+# undef DEBUG_X
 #endif

 #if DEBUG_LEVEL


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to