From: Eli Zaretskii <eliz@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: 11943@debbugs.gnu.org
Subject: bug#11943: 24.1.50; Emacs unusably slow when looking at large files (bidi support at fault)
Date: Sun, 15 Jul 2012 06:04:47 +0300 [thread overview]
Message-ID: <83k3y5bu7k.fsf@gnu.org> (raw)
In-Reply-To: <87vchp4zkk.fsf@shorty.local.i-did-not-set--mail-host-address--so-tickle-me>
> From: Dima Kogan <dima@secretsauce.net>
> Date: Sat, 14 Jul 2012 17:50:51 -0700
>
> I'm observing that when some large text files are loaded, emacs slows to
> a crawl. As an example, I have a 14MB file open (with emacs -Q). Every
> time I do (next-line) or (previous-line) it takes a few seconds. This is
> a > 2GHz Core2 machine, so there's no reason for this to happen. 'M-x
> benchmark' says that (previous-line) takes >2s each time. I discovered
> that if I do (setq bidi-display-reordering nil) then emacs is snappy
> again, with previous-line taking <1ms.
>
> The specific file I'm using to exhibit the bug consists of many repeated
> stanzas such as
>
> =========================
> {
> {2.222222,2.222222,2.222222,2.2},
> {-2.222222,2.222222,2.222222},
> {-22.222222,22.222222,2.222222}
> },
> =========================
>
> without the =. Saving a stanza into a file called 'snippet', the 14MB
> file can be made with
>
> $ for i in `seq 17`; do cat snippet snippet > xxx; mv xxx snippet; done
What is the major mode in the buffer where you see this? I mean the
real-life example where you bumped into this, not the 'snippet' file
produced by the above.
next prev parent reply other threads:[~2012-07-15 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 0:50 bug#11943: 24.1.50; Emacs unusably slow when looking at large files (bidi support at fault) Dima Kogan
2012-07-15 3:04 ` Eli Zaretskii [this message]
2012-07-15 3:31 ` Dima Kogan
2012-07-15 14:47 ` Eli Zaretskii
2012-07-15 11:58 ` Lawrence Mitchell
2012-07-15 14:51 ` Eli Zaretskii
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=83k3y5bu7k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11943@debbugs.gnu.org \
--cc=dima@secretsauce.net \
/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).