>From 49288975a810d1f2186f656cede92db93ee85c56 Mon Sep 17 00:00:00 2001 From: "Basil L. Contovounesios" Date: Wed, 31 Jan 2018 23:23:49 +0000 Subject: [PATCH] Clarify byte-compilation of "Custom Themes" in Elisp manual * doc/lispref/customize.texi (Custom Themes): Clarify status of byte-compiled custom themes. Suggested in https://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00824.html. --- doc/lispref/customize.texi | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/lispref/customize.texi b/doc/lispref/customize.texi index 6c7ca260ab..7fea507fd0 100644 --- a/doc/lispref/customize.texi +++ b/doc/lispref/customize.texi @@ -1432,7 +1432,9 @@ Custom Themes 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: -- 2.15.1