Re: DOCBOOK-APPS: Slow startup of psgml emacs

[Dave Pawson <davep at dpawson dot freeserve dot co dot uk>]

At 12:36 17/05/2002 +0200, Steffen Maier wrote:

> > Is there any option or flag that would trace or profile what the startup
> > code is actually doing ?
>
>Yet another flag :-): Try starting up your Emacs instance with the command
>line parameter --debug-init. Alas, as the name already suggests it only
>gives debug information if something in the init functions faults.

init as in .emacs?
  Might have guessed, emacs is one of those bits of software that
'probably does what you want, just that you haven't found out how .... yet'.
(bit like docbook?)

>  I don't
>know of a real function-trace to follow the init stuff. At least some info
>is put into the minibuffer (under the status line) while starting up and
>loading different elisp packages. If you can read fast enough...
>
>As a last resort you might want to inspect your .emacs (or possibly _emacs
>with NTEmacs) and "simulate" what will be going on when executing the
>contents in an elisp interpreter.

Dave, if you put the cursor at the end of each line of the .emacs file,
hit C-x C-e, it will execute that statement, which is sort of slow-mo
debug?

Regards DaveP