From: Basil L. Contovounesios Date: Fri, 2 Feb 2018 14:22:53 +0000 (-0500) Subject: * doc/lispref/customize.texi (Custom Themes): Clarify .el preference. X-Git-Tag: emacs-26.1-rc1~267 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=59344c43a92347387126fbf11fe8b4099b9bcebc;p=emacs.git * doc/lispref/customize.texi (Custom Themes): Clarify .el preference. Copyright-paperwork-exempt: yes https://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00824.html. --- diff --git a/doc/lispref/customize.texi b/doc/lispref/customize.texi index 6c7ca260abc..7fea507fd03 100644 --- a/doc/lispref/customize.texi +++ b/doc/lispref/customize.texi @@ -1432,7 +1432,9 @@ where the list entries have the same meanings as in would be evaluated when loading the theme, but that is bad form. To protect against loading themes containing malicious code, Emacs displays the source file and asks for confirmation from the user -before loading any non-built-in theme for the first time. +before loading any non-built-in theme for the first time. As +such, themes are not ordinarily byte-compiled, and source files +always take precedence when Emacs is looking for a theme to load. The following functions are useful for programmatically enabling and disabling themes: