From 85a1e2f9278381ea2d95102f8fddb20f8eb0da0c Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sun, 17 Jun 2018 08:22:23 +0300 Subject: [PATCH] ; * etc/NEWS: Tweak a recently-added NEWS entry. --- etc/NEWS | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/etc/NEWS b/etc/NEWS index 39b8b5ca0c8..a77be110ffa 100644 --- a/etc/NEWS +++ b/etc/NEWS @@ -518,14 +518,21 @@ names" in the Tramp manual for full documentation of these facilities. * Incompatible Lisp Changes in Emacs 27.1 -+++ -** Theme settings generally aren't actually applied until a call to -`enable-theme-, either one made explicitly or implicitly through -`load-theme' with NO-ENABLE nil. This change has the effect of not -applying theme changes just because we load a lisp file containing a -theme specification. The previous behavior is preserved for the -special case of the `user' theme, which is frequently used for -ad-hoc customization. +--- +** Just loading a theme's file no longer activates the theme's settings. +Loading a theme with 'M-x load-theme' still activates the theme, as it +did before. However, loading the theme's file with "M-x load-file", +or using 'require' or 'load' in a Lisp program, doesn't actually apply +the theme's settings until you either invoke 'M-x enable-theme' or +type 'M-x load-theme'. (In a Lisp program, calling 'enable-theme' or +invoking 'load-theme' with NO-ENABLE argument omitted or nil has the +same effect of activating a theme whose file has been loaded.) The +special case of the 'user' theme is an exception: it is frequently +used for ad-hoc customizations, so the settings of that theme are by +default applied immediately. + +The variable 'custom--inhibit-theme-enable' controls this behavior; +its default value changed in Emacs 27.1. ** The 'repetitions' argument of 'benchmark-run' can now also be a variable. ** The FILENAME argument to 'file-name-base' is now mandatory and no -- 2.39.2