From: David <de_bb@arcor.de>
To: help-gnu-emacs@gnu.org
Subject: Re: How to Reduce Emacs Load Time
Date: Sun, 31 Aug 2008 21:10:45 +0200 [thread overview]
Message-ID: <87r685atl6.fsf@arcor.de> (raw)
In-Reply-To: e774cb69-8a94-44e4-9e12-215f02e4b0eb@o40g2000prn.googlegroups.com
formido <formido@gmail.com> writes:
> Thanks very much for that. In this case, by inspection I can tell
> CEDET is a major culprit.
Strange. I just benchmarked my CEDET init function and it takes about
half a second.
> Mind telling me how you load CEDET? I just used instruction they gave--
> you can see above what my *messages* looks like at init.
Yes, CEDET sets up lots of stuff, but not much is actually loaded, so it
shouldn't take much time. It consists of several packages, which were in
fact separated in earlier releases, but are now bundled to make
installation easier. This is why you see so many messages about
different packages being set up. Don't worry too much about it. :-)
I would strongly advise to use CEDET from CVS. There have been huge
improvements since 1.0pre4, and Eric (Ludlam) is currently preparing a
1.0pre5 release based on the current CVS code.
You can check out the CVS version from sourceforge:
cvs -z3 -d:pserver:anonymous@cedet.cvs.sourceforge.net:/cvsroot/cedet co -P cedet
I usually defer loading CEDET until I load up a source file. You can use
something like this:
(defun my-init-cedet ()
(interactive)
(unless (fboundp 'cedet-version)
(load-file (expand-file-name "~/cedet/common/cedet.el"))
(semantic-load-enable-gaudy-code-helpers)
;; stickyfunc irritates me, so deactivate it
(global-semantic-stickyfunc-mode -1)
))
Then use e.g.
(eval-after-load "cc-mode"
'(my-init-cedet))
to load CEDET when CC-mode gets loaded. You can add this for several
other modes if you want to. You can also call this init manually.
-David
next prev parent reply other threads:[~2008-08-31 19:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 21:11 How to Reduce Emacs Load Time formido
2008-08-30 22:00 ` Pascal J. Bourguignon
2008-08-31 11:26 ` Nikolaj Schumacher
[not found] ` <mailman.18041.1220182012.18990.help-gnu-emacs@gnu.org>
2008-08-31 17:39 ` formido
2008-08-31 22:24 ` Nikolaj Schumacher
2008-08-31 17:50 ` formido
2008-09-08 12:38 ` Eric Ludlam
2008-08-30 22:05 ` Pascal J. Bourguignon
2008-08-30 22:03 ` formido
2008-08-31 11:59 ` Joost Diepenmaat
2008-08-31 9:39 ` Ivan Kanis
2008-08-31 12:35 ` Nikolaj Schumacher
[not found] ` <mailman.18043.1220186144.18990.help-gnu-emacs@gnu.org>
2008-08-31 20:01 ` Chetan
2008-08-31 11:39 ` David
[not found] ` <mailman.18042.1220182790.18990.help-gnu-emacs@gnu.org>
2008-08-31 17:42 ` formido
2008-08-31 19:10 ` David [this message]
2008-08-31 22:10 ` Nikolaj Schumacher
2008-08-31 22:20 ` David
[not found] ` <mailman.18077.1220220611.18990.help-gnu-emacs@gnu.org>
2008-08-31 22:36 ` formido
2008-09-02 18:04 ` Ken Goldman
2008-09-03 13:06 ` rustom
2008-09-03 17:06 ` Rupert Swarbrick
2008-09-04 11:01 ` rustom
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=87r685atl6.fsf@arcor.de \
--to=de_bb@arcor.de \
--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).