Bug 78666 - slow reaction to key presses once the line gets too long
Summary: slow reaction to key presses once the line gets too long
Status: RESOLVED DUPLICATE of bug 64569
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-29 14:16 UTC by kaiser_johannes
Modified: 2004-12-17 18:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kaiser_johannes 2004-03-29 14:16:34 UTC
Version:            (using KDE KDE 3.1.4KDE 1.2)
Installed from:    SuSE RPMsSuSE RPMs
OS:          Linux

One thing which I couldn't help noticing is that the longer the
edited line is, the slower the editor reacts to key presses. If a
paragraph gets too long, it's almost impossible to type without
inserting CRs occasionally.
Comment 1 Jens Dagerbo 2004-03-29 14:20:29 UTC
I never noticed that...

How long is "too long"? And what, if any, syntax highlighting type is active?
Comment 2 kaiser_johannes 2004-03-29 15:12:43 UTC
> How long is "too long"? And what, if any, syntax highlighting type is active?
> 
This problem occurs in the program kile, with lines of about 2k length. 
Syntax highlighting ist activated.

Comment 3 Jeroen Wijnhout 2004-03-29 15:43:17 UTC
On Monday 29 March 2004 15:12, kaiser_johannes@yahoo.de wrote:
> > How long is "too long"? And what, if any, syntax highlighting type is
> > active?
>
> This problem occurs in the program kile, with lines of about 2k length.
> Syntax highlighting ist activated.

Note that Kile uses a different syntax highlighting for LaTeX than the native 
Kate highlighting. The latex-kile.xml is optimized (in the sense that it uses 
#pop and $push, reducing the use of the stack) and not significantly slower 
than the latex.xml file.

The latex-kile.xml is located at:
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdeextragear-2/kile/kile/syntax/latex-kile.xml

Checking with a 10.000 character line, I can confirm things are slow. The more 
syntax highlighting is going on, the slower it gets. latex-kile.xml seems 
some what slower than latex.xml here. I guess it is because latex-kile.xml is 
more thorough/complex than latex.xml.

However in constructing the 10.000 c line caused Kate to become very laggy, it 
seems Kate is just not fast when dealing with long lines. Admitted, the line 
is ridiculously long.

best,
Jeroen
Comment 4 Dominik Haumann 2004-03-29 17:04:04 UTC
it is a duplicate of #64569 - a known issue, and still slow in CVS HEAD.

*** This bug has been marked as a duplicate of 64569 ***
Comment 5 Anders Lund 2004-03-29 20:36:57 UTC
Could you provide a sample file?
Questions:
* does it matter if you type in the beginning, middle or end of the line?
* is the file syntax highlighted, and does it help turning that off (setting the syntax highlight to 'normal')?

Comment 6 Gabor Fekete 2004-12-17 18:47:00 UTC
It is not only for very long lines. Kate makes the CPU work 100% when "left"ing (moving right) in a line as long as 147 (editing a bash script of 6 lines). The problem occurs only after around the 10th column (or character). I would not call 147 a huge number. So, something really sucks with Kate. 
It makes my xmms choke. :(

May be related: http://bugs.kde.org/show_bug.cgi?id=93928