From: Eli Zaretskii <eliz@gnu.org>
To: Randy Yates <yates@digitalsignallabs.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs takes exhorbitantly long to read long, one-line files.
Date: Sun, 19 May 2013 17:41:32 +0300 [thread overview]
Message-ID: <8338tjxc9v.fsf@gnu.org> (raw)
In-Reply-To: <87ppwn62yr.fsf@digitalsignallabs.com>
> From: Randy Yates <yates@digitalsignallabs.com>
> Date: Sat, 18 May 2013 23:52:28 -0400
>
> I have a file (a matlab .m file of a vector of data) that is all on
> one line and about 2 MB:
>
> http://www.digitalsignallabs.com/dspin.m
>
> emacs takes a very long time (6 minutes?) to read this in, and
> practically becomes unusable in the mean time.
I think most of the time is taken by display, not by actually reading
the file.
> I'm thinking of looking into the code to get an idea of why this happens
> and of course look for a fix. If anyone has any pointers or other info
> on the problem, please inform me.
It's a long known problem, whose reasons are closely related to the
implementation of the Emacs display engine. See
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13675#8
next prev parent reply other threads:[~2013-05-19 14:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 3:52 emacs takes exhorbitantly long to read long, one-line files Randy Yates
2013-05-19 14:41 ` Eli Zaretskii [this message]
2013-05-20 8:40 ` Dmitry Antipov
2013-05-20 11:03 ` Randy Yates
2013-05-20 11:27 ` Dmitry Antipov
2013-05-20 14:32 ` Karl Fogel
2013-05-20 15:59 ` Eli Zaretskii
2013-05-20 16:25 ` Dmitry Antipov
2013-05-20 16:41 ` Eli Zaretskii
2013-05-20 21:43 ` Randy Yates
2013-05-21 2:21 ` Stephen J. Turnbull
2013-05-21 2:47 ` Eli Zaretskii
2013-05-21 7:57 ` Ulrich Mueller
2013-05-21 10:20 ` Dmitry Antipov
2013-05-21 12:06 ` Ulrich Mueller
2013-05-21 17:21 ` Eli Zaretskii
2013-05-21 17:18 ` Eli Zaretskii
2013-05-21 17:55 ` Eli Zaretskii
2013-05-21 18:03 ` Randy Yates
2013-05-21 18:28 ` Dmitry Antipov
2013-05-22 5:10 ` Ulrich Mueller
2013-05-22 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=8338tjxc9v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yates@digitalsignallabs.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).