[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/doc/emacs/custom.texi,v
From: |
Glenn Morris |
Subject: |
[Emacs-diffs] Changes to emacs/doc/emacs/custom.texi,v |
Date: |
Sat, 05 Apr 2008 18:39:22 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Glenn Morris <gm> 08/04/05 18:39:21
Index: custom.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/emacs/custom.texi,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- custom.texi 29 Jan 2008 06:54:27 -0000 1.6
+++ custom.texi 5 Apr 2008 18:39:21 -0000 1.7
@@ -2085,10 +2085,14 @@
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}.
- [Emacs-diffs] Changes to emacs/doc/emacs/custom.texi,v,
Glenn Morris <=