Mercurial > hg > xemacs-beta
view info/dir @ 1298:1b4bc72f433e
[xemacs-hg @ 2003-02-14 12:05:06 by ben]
speedups to build process
autoload.el: Factor out common code in generate-{c-,}file-autoloads-1 into new
function generate-autoload-ish-1. \(I was originally going to use
this for custom as well but ended up thinking better of it.)
cus-dep.el: Cache the old computed values in custom-load.el and reuse them as
necessary, to speed up running cus-dep (which would take 25-30
seconds to do all files in lisp/*, lisp/*/* on my Pentium III
700). Use `message' not `princ' to get correct newline behavior.
Output messages showing each file we do actually process.
update-elc-2.el: Rewrite algorithm to be much faster -- cache calls to
directory-files and don't make needless calls to file-exists-p,
file-directory-p because they're way way slow.
Autoload early and only when update-elc has told us to.
update-elc.el: If no files need byte compilation, signal to update-elc-2 to do
any necessary autoload updating (using the file REBUILD_AUTOLOADS)
rather than doing it ourselves, which would be way slow. Ignore
updates to custom-load.el and auto-autoloads.el when checking to
see whether autoloads need updating. Optimize out many
unnecessary calls to file-exists-p to speed it up somewhat. (####
The remaining time is 50% or more in locate-file; this is
presumably because, even though it has a cache, it's still
statting each file to determine it's actually there. By calling
directory-files ourselves, building a tree, and then looking in
that tree, we could drastically shorten the time needed to do the
locate operation.)
| author | ben |
|---|---|
| date | Fri, 14 Feb 2003 12:05:07 +0000 |
| parents | f5d8712231af |
| children | c2580215c222 |
line wrap: on
line source
-*- Text -*- This is the file .../info/dir, which contains the topmost node of the Info hierarchy. The first time you invoke Info you start off looking at that node, which is (dir)Top. Rather than adding new nodes to this directory (and this file) it is a better idea to put them in a site-local directory, and then configure info to search in that directory as well. That way, you won't have to re-edit this file when a new release of the editor comes out. For example, you could add this code to .../lisp/site-start.el, which is loaded before ~/.emacs each time the editor starts up: ;; find local info nodes (setq Info-directory-list (append Info-directory-list '("/private/info/"))) Then, when you enter info, a dir file like this one will be automatically created and saved (provided you have write access to the directory). The contents of that file "/private/info/dir" will be appended to the contents of this file. File: dir Node: Top This is the top of the INFO tree This is Info, the online documentation browsing system. This page (the Directory node) gives a menu of major topics. button2 on a highlighted word follows that cross-reference. button3 anywhere brings up a menu of commands. ? lists additional keyboard commands. h invokes the Info tutorial. * Menu: XEmacs 21.5 =========== * XEmacs:: XEmacs User's Manual. * Lispref:: XEmacs Lisp Reference Manual. * New-Users-Guide:: Getting Started with XEmacs. * XEmacs-FAQ:: XEmacs Frequently Asked Questions for 21.4. * Info:: Guide to Info, the XEmacs online documentation system. * Internals:: Guide to the internals of XEmacs. Other Documentation: * CL:: A Common Lisp compatibility package for Emacs-Lisp. * Custom:: Customization Library for Emacs. * Emodules:: XEmacs dynamically loadable module support. * External-Widget:: Use XEmacs as a text widget inside of another program. * Standards:: GNU coding standards. * Term:: A mode to control inferior processes (a comint replacement) * Termcap:: The termcap library, which enables application programs to handle all types of character-display terminals. * Texinfo:: The GNU documentation format. * Widget:: An Emacs Lisp widget library.