all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aleksey Cherepanov <aleksey.4erepanov@gmail.com>
Cc: 16800@debbugs.gnu.org
Subject: bug#16800: 24.3; flyspell works slow on very short words at the end of big file
Date: Fri, 21 Feb 2014 12:15:00 +0200	[thread overview]
Message-ID: <83ob204vrv.fsf@gnu.org> (raw)
In-Reply-To: <85zjlo5ecy.fsf@gmail.com>

> From: Aleksey Cherepanov <aleksey.4erepanov@gmail.com>
> Date: Wed, 19 Feb 2014 00:56:45 +0400
> 
> I faced a problem editing my big .org file (2mb+) with flyspell-mode
> enabled. I edit it every day, regularly mistype and get words of one
> or two letters that are wrong in Russian and cause flyspell work slow.
> 
> This one-liner produces "good" file to reproduce the bug.
> perl -e 'print(((join " ", ("met and") x 10) . "\n") x 30000)' > t.txt
> 
> Typing "nd" at the end of file gives a huge pause even on a fast
> computer. But "mw" or "md" does not give pauses because they are not
> substrings in this file. It is repeatable with emacs -Q.

This seems to be due to the Flyspell's feature of recognizing
duplicates of mis-spelled words, and, if found, highlighting such
duplicates in a different face.  If you customize the variable
flyspell-duplicate-distance to some small value (or even zero), the
delay goes away.  Evidently, with the default value of -1, Flyspell
searches all the way to the beginning of the giant buffer, looking for
a duplicate of "nd".

Interestingly, I don't see this when the speller is Ispell, but I do
see it with Hunspell.  Not sure how using Ispell avoids this problem.





  reply	other threads:[~2014-02-21 10:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 20:56 bug#16800: 24.3; flyspell works slow on very short words at the end of big file Aleksey Cherepanov
2014-02-21 10:15 ` Eli Zaretskii [this message]
2014-02-21 14:38   ` Agustin Martin
2014-02-21 15:12     ` Eli Zaretskii
2014-02-21 15:21       ` Eli Zaretskii
2014-02-22 12:44       ` Aleksey Cherepanov
2014-02-22 13:10         ` Eli Zaretskii
2014-02-22 16:02           ` Aleksey Cherepanov
2014-02-22 16:41             ` Eli Zaretskii
2014-02-22 18:55               ` Aleksey Cherepanov
2014-02-22 20:16                 ` Aleksey Cherepanov
2014-02-22 21:03                 ` Eli Zaretskii
2014-02-23  1:26                   ` Agustin Martin
2014-02-23 18:36                     ` Eli Zaretskii
2014-02-23 19:56                     ` Aleksey Cherepanov
2014-02-23 23:02                       ` Aleksey Cherepanov
2014-02-24 16:03                         ` Aleksey Cherepanov
2014-02-26 20:32                           ` Agustin Martin
2014-02-28 11:45                             ` Agustin Martin
2014-02-28 11:51                               ` Eli Zaretskii
2014-03-01 21:44                                 ` Aleksey Cherepanov
2014-03-02  3:56                                   ` Eli Zaretskii
2014-03-09 17:36                                     ` Agustin Martin
2014-03-09 18:02                                       ` Aleksey Cherepanov
2014-03-09 18:24                                         ` Eli Zaretskii
2014-02-28 23:11                               ` Aleksey Cherepanov
2014-03-01 10:33                                 ` Aleksey Cherepanov
2014-03-01 15:50                                   ` Aleksey Cherepanov
2014-03-01 21:39                                 ` Aleksey Cherepanov
2014-03-09 17:25                                 ` Agustin Martin
2015-03-06 21:46                                   ` Agustin Martin
2015-03-07  8:09                                     ` Eli Zaretskii
2014-02-23 20:39                     ` Aleksey Cherepanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ob204vrv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16800@debbugs.gnu.org \
    --cc=aleksey.4erepanov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.