Bug#47527: marked as done (kate still sluggish when opening large or many files) by John Firebaugh <[email protected]>

Your message with subj: Bug#47527: kate still sluggish when opening large or many files

On Friday 06 September 2002 6:41, [email protected] wrote:
> Package: kate
> Version: KDE 3.0.3
> Severity: normal
> Installed from:    RedHat RPMs
> Compiler:          Not Specified
> OS:                Linux
> OS/Compiler notes: binaries were downloaded from kde mirror
>
> A while ago I reported bug #42945. I was told it was fixed. In the mean
> time 3.0.3 came out and I downloaded the RedHat binaries from a kde mirror,
> and the problem is still there.

Fixed means fixed in CVS HEAD, which means it will be released as 3.1. You 
might want to try the 3.1alpha1 release.

has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

(Complete bug history is available at http://bugs.kde.org/db/47/47527.html)

Received: (at submit) by bugs.kde.org; 6 Sep 2002 13:41:19 +0000
Received: (qmail 7336 invoked by uid 30); 6 Sep 2002 13:41:18 -0000
Date: 6 Sep 2002 13:41:18 -0000
Message-ID: <[email protected]>
To: [email protected]
Subject: kate still sluggish when opening large or many files
From: [email protected]
X-KDE-Received: -216.165.3.171

Package:           kate
Version:           KDE 3.0.3 
Severity:          normal
Installed from:    RedHat RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: binaries were downloaded from kde mirror

A while ago I reported bug #42945. I was told it was fixed. In the mean time 3.0.3 came out and I downloaded the RedHat binaries from a kde mirror, and the problem is still there.

(Submitted via bugs.kde.org)