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: Sun, 09 Mar 2014 20:24:33 +0200 [thread overview]
Message-ID: <8361nnp6vy.fsf@gnu.org> (raw)
In-Reply-To: <20140309180244.GA24331@openwall.com>
> Date: Sun, 9 Mar 2014 22:02:44 +0400
> From: Aleksey Cherepanov <aleksey.4erepanov@gmail.com>
> Cc: 16800@debbugs.gnu.org
>
> On Sun, Mar 09, 2014 at 06:36:55PM +0100, Agustin Martin wrote:
> > 2014-03-02 4:56 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:
> >
> > > > Date: Sun, 2 Mar 2014 01:44:27 +0400
> > > > From: Aleksey Cherepanov <aleksey.4erepanov@gmail.com>
> > > > Cc: Agustin Martin <agustin.martin@hispalinux.es>, 16800@debbugs.gnu.org
> > > >
> > > > We could try to limit execution time. Though checks for that could
> > > > slow down the search.
> > >
> > > Exactly.
> > >
> >
> > I see other problem with that, it is not deterministic, since the limit
> > depends on system load.
>
> We may have limit by time with additional limit for lowest radius so
> the search works not less than for N chars and if it looks further
> then not more than M milliseconds.
FWIW, I think this would be over-engineering. Emacs never does
anything like that, we always have simple, deterministic limits in
terms of characters or lines. This makes it easy for users to
customize their sessions in a way whose effect is simple to understand
and predictable.
next prev parent reply other threads:[~2014-03-09 18:24 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8361nnp6vy.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).