From: Lennart Borgman <lennart.borgman@gmail.com>
To: "Pascal J. Bourguignon" <pjb@informatimago.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Poor Performance w/ Long Files
Date: Thu, 20 Aug 2009 02:52:59 +0200 [thread overview]
Message-ID: <e01d8a50908191752i71e91c6ax98f77ee097afa6e5@mail.gmail.com> (raw)
In-Reply-To: <87skfnwdkv.fsf@galatea.local>
On Thu, Aug 20, 2009 at 2:09 AM, Pascal J.
Bourguignon<pjb@informatimago.com> wrote:
> Tim Visher <tim.visher@gmail.com> writes:
>
>> Hello Everyone,
>>
>> I work with many large files (+10,000,000 ASCII characters) at work
>> and I've noticed that Emacs does extremely poorly with those files. I
>> have taken to opening them up in something like Notepad++ to look at
>> them and editing the programs that operate on them in Emacs. I'd love
>> to be able to just stick with Emacs.
>>
>> Is there something that I just haven't set yet or does Emacs have
>> trouble with large files?
>
> Perhaps you could disable some emacs options that might take time,
> like font-locking. Basically, if you edit this files in fundamental-mode,
> with truncate-line turned off with C-u 1 M-x toggle-truncate-lines RET and
> with font-locking turned off with C-u -1 M-x font-lock-mode RET,
> it should go faster.
I think we recently got a bug report where the user was using
fundamental-mode to edit a file with very long lines. That was very
slow.
If I remember correctly that depends on how the display engine in
Emacs is organized. It searches for line ends. If I understand Stefan
Monnier correctly this is something that can be cured and have a
rather high priority. So if someone want to jump in and have enough
knowledge to understand this it is probably welcome. (It might be a
difficult problem.)
next prev parent reply other threads:[~2009-08-20 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4876.1250712802.2239.help-gnu-emacs@gnu.org>
2009-08-20 0:09 ` Poor Performance w/ Long Files Pascal J. Bourguignon
2009-08-20 0:52 ` Lennart Borgman [this message]
2009-08-20 12:16 ` Tim Visher
[not found] ` <mailman.4884.1250770619.2239.help-gnu-emacs@gnu.org>
2009-08-20 13:50 ` Pascal J. Bourguignon
2009-08-20 16:24 ` Tim Visher
2009-08-20 16:38 ` Stefan Vollmar
2009-08-19 20:12 Tim Visher
2009-08-19 20:18 ` 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=e01d8a50908191752i71e91c6ax98f77ee097afa6e5@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pjb@informatimago.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.
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).