From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17837@debbugs.gnu.org
Subject: bug#17837: 24.4.50; Search very slow
Date: Tue, 24 Jun 2014 11:42:13 -0400 [thread overview]
Message-ID: <E1WzSrN-0006ul-1w@fencepost.gnu.org> (raw)
In-Reply-To: <834mzbrplv.fsf@gnu.org> (message from Eli Zaretskii on Tue, 24 Jun 2014 05:46:52 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Yes, I see some slowdown wrt 23.2, although not as drastic. Are you
sure both binaries were compiled similarly, e.g. as far as compiler
optimization switches are concerned?
Perhaps not. The 23.2 was not built by me. I picked it because it was
the oldest I have.
Anyway, you may wish to experiment with setting jit-lock-defer-time to
a non-nil value. E.g., try setting it to 0.25 or 0.5 sec, and see if
that gives good results.
I tried setting that to .1, and here's what happened.
I typed C-s C-s (which searched for "honor"). It found the first
occurrence and displayed it without fontifying that area.
Then I typed C-f and got no response. I suspect it had already
started to highlight the other matches, and was fontifying the
regions where they occur.
The C-f was executed after 30 seconds or more.
The current code gives bad results with all settings of that variable.
The code needs to be fixed.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
next prev parent reply other threads:[~2014-06-24 15:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 15:26 bug#17837: 24.4.50; Search very slow Richard Stallman
2014-06-23 15:47 ` Eli Zaretskii
2014-06-23 16:32 ` Eli Zaretskii
2014-06-23 15:51 ` Stefan Monnier
2014-06-23 16:38 ` Eli Zaretskii
2014-06-23 21:15 ` Stefan Monnier
2014-06-24 1:08 ` Richard Stallman
2014-06-24 2:46 ` Eli Zaretskii
2014-06-24 15:06 ` Stefan Monnier
2014-06-24 15:43 ` Richard Stallman
2014-06-24 15:42 ` Richard Stallman [this message]
2014-06-24 15:59 ` Eli Zaretskii
2014-06-24 17:29 ` Stefan Monnier
2014-06-25 11:28 ` Richard Stallman
2014-06-25 11:28 ` Richard Stallman
2014-06-25 13:28 ` Eli Zaretskii
2014-06-26 0:10 ` Richard Stallman
2014-06-26 2:54 ` Stefan Monnier
2014-06-26 18:39 ` Richard Stallman
2014-06-26 14:59 ` Eli Zaretskii
2014-06-26 18:40 ` Richard Stallman
2021-09-19 22:14 ` Stefan Kangas
2021-09-20 6:10 ` Lars Ingebrigtsen
2021-09-20 6:56 ` Stefan Kangas
2021-09-21 22:15 ` Richard Stallman
2021-09-21 22:16 ` Lars Ingebrigtsen
2021-09-20 23:51 ` Richard Stallman
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=E1WzSrN-0006ul-1w@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=17837@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).