From: Tim Visher <tim.visher@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 12:24:10 -0400 [thread overview]
Message-ID: <c115fd3c0908200924sad5902dxb5afeae297c5fd39@mail.gmail.com> (raw)
In-Reply-To: <7cr5v64msw.fsf@pbourguignon.anevia.com>
On Thu, Aug 20, 2009 at 9:50 AM, Pascal J.
Bourguignon<pjb@informatimago.com> wrote:
> Tim Visher <tim.visher@gmail.com> writes:
>
>> On Wed, Aug 19, 2009 at 8:09 PM, 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.
>>
>> This fixed things. I hadn't even thought of it but the file I was
>> opening tried to open in tcl and pabbrev modes and that's what seems
>> to have caused the slowdown. Putting thing back into Fundamental with
>> pabbrev off quickened things right up.
>>
>> Is there a way to manually force a file to open in a particular mode
>> without setting an auto-mode in .emacs?
>
> M-x find-file-literally RET
>
> It's written right down at the bottom of the help page for find-file ;-)
>
> To visit a file without any kind of conversion and without
> automatically choosing a major mode, use M-x find-file-literally.
Thanks! I should've checked the manual myself first. :)
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
next prev parent reply other threads:[~2009-08-20 16:24 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c115fd3c0908200924sad5902dxb5afeae297c5fd39@mail.gmail.com \
--to=tim.visher@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.