[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#4511: marked as done (23.1; flyspell-mode slow editing near end of b
Emacs bug Tracking System
bug#4511: marked as done (23.1; flyspell-mode slow editing near end of big html file)
Wed, 23 Sep 2009 23:15:03 +0000
Your message dated Wed, 23 Sep 2009 19:06:04 -0400
with message-id <address@hidden>
and subject line Re: bug#4511: 23.1; flyspell-mode slow editing near end of big
has caused the Emacs bug report #4511,
regarding 23.1; flyspell-mode slow editing near end of big html file
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message ---
23.1; flyspell-mode slow editing near end of big html file
Tue, 22 Sep 2009 08:24:38 +1000
Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
When flyspell-mode is enabled in a big html file, and point is somewhere
near the end of the buffer, typing text or moving point with C-f and C-b
become sluggish, to the point of being nearly unusable.
(This is a regression from emacs 22, where flyspell-mode was fine on
I expect "big file" is relative to cpu speed, but 300 kbytes is bad on
my slow pc (not an outrageously huge file). To reproduce try this of
about 600 kbytes,
(dotimes (i 50000) (insert (format "<p> abc def\n" i)))
It takes a few seconds to create the buffer, but of course that's not
the bug. The bad bit is if you move point around with C-f / C-b near
the end of the buffer, or type some plain text there outside of a <tag>,
where it's sluggish between keystrokes. (Try upping the 50000 on a fast
cpu if necessary.)
I track the slowness to where `sgml-mode-flyspell-verify' does
I take it this func is asking whether point is within a <tag> or not.
Does that regexp end up asking re-search-backward to consider every "<"
in the buffer or something, before deciding no match is possible?
I find it hugely faster to do an old fashioned skip-chars-backward as
below -- assuming I'm not mistaken that the "\n" in the existing
`looking-back' is supposed mean examining no more than the current line.
2009-09-21 Kevin Ryde <address@hidden>
* textmodes/flyspell.el (sgml-mode-flyspell-verify): Use
skip-chars-backward instead of looking-back, to avoid a very slow
regexp match when far into a big buffer with a lots of "<" chars.
--- flyspell.el.~1.146.~ 2009-09-18 08:23:13.000000000 +1000
+++ flyspell.el 2009-09-21 16:36:12.000000000 +1000
@@ -363,7 +363,9 @@
"Function used for `flyspell-generic-check-word-predicate' in SGML mode."
(or (looking-at "[^<\n]*>")
- (ispell-looking-back "<[^>\n]*")
+ (skip-chars-backward "^<>\n") ;; \n only look at current line
+ (not (equal ?< (char-before)))) ;; "<" if in a tag
(and (looking-at "[^&\n]*;")
In GNU Emacs 23.1.1 (i486-pc-linux-gnu, GTK+ Version 2.16.5)
of 2009-08-03 on raven, modified by Debian
configured using `configure '--build=i486-linux-gnu' '--host=i486-linux-gnu'
'--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib'
'--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars'
'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -g
-O2' 'LDFLAGS=-g' 'CPPFLAGS=''
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_AU
value of $XMODIFIERS: nil
--- End Message ---
--- Begin Message ---
Re: bug#4511: 23.1; flyspell-mode slow editing near end of big html file
Wed, 23 Sep 2009 19:06:04 -0400
Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)
>>> You need to pass it a `limit' argument.
>> I thought about that a bit. The limit would be the immediately
>> preceding "<", ">", or "\n", since whichever of them is hit first
>> answers whether you're in a tag or not.
> (line-beginning-position) will do fine.
--- End Message ---