From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs/prelude: lag in opening big files
Date: Fri, 21 Jul 2017 10:34:57 -0400 [thread overview]
Message-ID: <jwvvamleu87.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 25646CD8-2C85-4840-B72F-8B2EE79D9349@agrarianresearch.org
> I am having a strange problem that I have never faced before.
> When I open (C-f) a large file, it gets stuck for a long time. I have
> to wait for eternity before the file would open. But if I C-g and
> cancel the process, and do it again, the second time, it opens in
> a snap.
That's because the C-g doesn't kill the "not quite finished" new buffer.
And the second time around find-file encounters the "not quite finished"
buffer, has no idea it's "not quite finished" and just displayed it as
it is without further ado.
> How do I debug this?
M-: (setq debug-on-error t debug-on-quit t)
C-f ../new-big-file
C-g
should give you a backtrace which shows what Emacs is in the process
of doing.
Stefan
prev parent reply other threads:[~2017-07-21 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 2:07 Emacs/prelude: lag in opening big files Vikas Rawal
2017-07-21 13:43 ` Eli Zaretskii
2017-07-21 14:34 ` Stefan Monnier [this message]
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=jwvvamleu87.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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.
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).