From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: help-gnu-emacs@gnu.org
Subject: Emacs/prelude: lag in opening big files
Date: Fri, 21 Jul 2017 07:37:55 +0530 [thread overview]
Message-ID: <25646CD8-2C85-4840-B72F-8B2EE79D9349@agrarianresearch.org> (raw)
I have recently shifted to using prelude for my emacs configuration.
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.
I have tried it with many files, and it happens each time. If a file is opened and closed, and I want to open it again, emacs does the same thing all over again. That is, slow to open first time, but opens in a snap if I C-g and start again.
How do I debug this? I tried to use profiler to figure out where was emacs stuck. Below is the main part of the report on cpu usage when I tried to open a large org mode file. Looks like helm is one of the culprits. Is this usual? Is there a way to deal with this?
Vikas
- command-execute 6903 57%
- call-interactively 6903 57%
- funcall-interactively 6575 54%
- helm-find-files 6575 54%
- helm-find-files-1 6575 54%
- helm 6575 54%
- apply 6575 54%
- helm 6575 54%
- apply 6575 54%
- helm-internal 6575 54%
- helm-execute-selection-action 6103 50%
- helm-execute-selection-action-1 6103 50%
- helm-find-file-or-marked 6102 50%
- apply 6102 50%
+ #<compiled 0x40bf3dad> 6102 50%
+ helm-get-actions-from-current-source 1 0%
+ helm-read-pattern-maybe 470 3%
+ helm-initialize 1 0%
+ #<compiled 0x43fa6779> 1 0%
+ byte-code 328 2%
- timer-event-handler 5047 41%
- apply 5047 41%
- org-indent-initialize-agent 5042 41%
- org-indent-initialize-buffer 5041 41%
- org-indent-add-properties 5030 41%
- org-indent-set-line-properties 1159 9%
org-add-props 1 0%
- org-at-item-p 29 0%
+ org-list-in-valid-context-p 26 0%
org-list-item-body-column 1 0%
org-current-level 1 0%
#<compiled 0x40495149> 1 0%
cancel-timer 1 0%
+ savehist-autosave 4 0%
auto-revert-buffers 1 0%
Vikas
next reply other threads:[~2017-07-21 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 2:07 Vikas Rawal [this message]
2017-07-21 13:43 ` Emacs/prelude: lag in opening big files Eli Zaretskii
2017-07-21 14:34 ` Stefan Monnier
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=25646CD8-2C85-4840-B72F-8B2EE79D9349@agrarianresearch.org \
--to=vikaslists@agrarianresearch.org \
--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).