procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(Init File): Byte-compiling .emacs is bad.

Browse source
This commit is contained in:
Glenn Morris 2008-04-05 18:39:33 +00:00
parent 185ae1f1d0
commit 06a97d46c4
2 changed files with 12 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/emacs/ChangeLog
View file

@ -1,3 +1,7 @@
2008-04-05 Glenn Morris <rgm@gnu.org>
* custom.texi (Init File): Byte-compiling .emacs is bad.
2008-04-04 Stefan Monnier <monnier@iro.umontreal.ca>
* mini.texi (Minibuffer Edit) <resize-mini-windows>: Adjust default.

12
doc/emacs/custom.texi
View file

@ -2085,10 +2085,14 @@ Many sites put these files in the @file{site-lisp} subdirectory of the
Emacs installation directory, typically
@file{/usr/local/share/emacs/site-lisp}.
If you have a large amount of code in your @file{.emacs} file, you
should rename it to @file{~/.emacs.el}, and byte-compile it. @xref{Byte
Compilation,, Byte Compilation, elisp, the Emacs Lisp Reference Manual},
for more information about compiling Emacs Lisp programs.
Byte-compiling your @file{.emacs} is not recommended (@pxref{Byte
Compilation,, Byte Compilation, elisp, the Emacs Lisp Reference
Manual}). It generally does not speed up startup very much, and often
leads to problems when you forget to recompile the file. A better
solution is to use the Emacs server to reduce the number of times you
have to start Emacs (@pxref{Emacs Server}). If your @file{.emacs}
defines many functions, consider moving them to a separate
(byte-compiled) file which you load in your @file{.emacs}.
If you are going to write actual Emacs Lisp programs that go beyond
minor customization, you should read the @cite{Emacs Lisp Reference Manual}.