On Sunday 01 January 2006 08:20 pm, Rogério Brito wrote:
> On Jan 01 2006, Mitchell Laks wrote:

> > How to dispense with it?
>
> Do you possibly have anything like ecb, semantic, eieio, speedbar-*,
> cedet-* installed in your machine? If you don't have any use for them,
> I'd suggest you to uninstall those packages.

Dear Rogerio,

I thank you for your comments, and you are right, I did a mega install once on 
this machine of all of the stuff i  found in Quantian because I wanted 
"IT ALL". Every development thing.  Hell of a lot of stuff.

And there are many cool linux development toys, as we all know - thats why we 
LOVE debian!

I periodically wondered about this slow start up issue. 

This time, after I wrote that message,  I started googling and discovered how 
I can actually find out what happens in startup.

I did C-x C-b and chose the buffer *Messages*. 

Indeed on the slow machine I was loading about 48 different things, all 
development stuff like semantic eieio etc.  I am working on some open source 
development projects and hope to need some of them :).

Now I noticed that in fact, over time, I had gotten rid of some of those 
things from my debian system, and while they were no longer on my system - 
like cedet-common, they still wanted to load in emacs and I was "wasting 
loading time" while it errored out. In fact, adding the cedet-common back 
onto my system made the loading faster  (only 4 seconds now) :).

So this suggests a few thoughts:

1) packaging flaws - stuff was removed and but still did not clean up side 
effects on emacs effects.

2) If I want to "keep" stuff but let them be loaded after emacs comes up, can 
that be done? It would seem that most of these things could rather be loaded 
after I am working, then I wouldn't notice the wait. 

Why must I wait 4 seconds up front? It takes me at least 4 seconds to get any 
text  written, and it is annoying to watch the startup.

3) where in emacs can I control the load list.

4) for your amusement, I will show you the long list on my machine. It is 
truly embarrassing.  I notice that I still get errors. For instance notice: 
ecb seems unhappy still.

Loading 50a2ps (source)...done
Loading 50aribas (source)...done
Loading 50auctex (source)...done
Loading 50autoconf (source)...done
Loading 50cedet-common (source)...
Loading advice...done
Loading 50cedet-common (source)...done
Loading 50dictionaries-common (source)...
Loading debian-ispell...
Loading /var/cache/dictionaries-common/emacsen-ispell-default.el 
(source)...done
Loading debian-ispell...done
Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...done
Loading 50dictionaries-common (source)...done
Loading 50eieio (source)...done
Loading 50ess (source)...
Loading regexp-opt...done
Loading mule-util...done
Loading ange-ftp...done
Loading 50ess (source)...done
Loading 50ftnchek (source)...done
Loading 50gri-el (source)...done
Loading 50gri-html-doc (source)...done
Loading 50maxima-emacs (source)...done
Loading 50mgp (source)...done
Loading 50mpqc-support (source)...done
Loading 50nowebm (source)...done
Loading 50octave (source)...done
Loading 50preview-latex (source)...done
Loading 50tramp (source)...done
Loading 50yacas (source)...done
Loading 50yorick-auto (source)...done
Loading 51ede (source)...done
Loading 51preview-latex (source)...
Loading preview-latex...done
Loading 51preview-latex (source)...done
Loading 51speedbar (source)...done
Loading 52semantic (source)...
Loading derived...done
Loading /usr/lib/emacs/21.4/i386-linux/fns-21.4.1-x.el (source)...done
Loading semantic-idle (source)...done [2 times]
Loading ede-speedbar (source)...done
Loading 52semantic (source)...done
Loading 53cedet-contrib (source)...done
Loading 53cogre (source)...done
Loading 55ecb (source)...
"/usr/share/emacs21/site-lisp/cedet-common/" added to `load-path'
Error while loading 55ecb
Loading semantic-el (source)...done
For information about the GNU Project and its goals, type C-h C-p.
call-interactively: Beginning of buffer [14 times]
call-interactively: End of buffer
>
>
> Hope this helps, Rogério.

Reply via email to