From: Eli Zaretskii <eliz@gnu.org>
Date: Sat, 27 Apr 2024 08:52:30 +0000 (+0300)
Subject: Improve documentation of 'package-enable-at-startup'
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=b0ff657c05e7e37e24f9afbf8917e8d8a3400e89;p=emacs.git

Improve documentation of 'package-enable-at-startup'

* doc/emacs/package.texi (Package Installation): Clarify how to
customize 'package-enable-at-startup'.

* lisp/emacs-lisp/package.el (package-enable-at-startup): Add note
about customization.  (Bug#70402)

(cherry picked from commit a7d51085cf0a6e6d01fa265001d7d6a4bd728ed2)
---

diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi
index c8f790bab47..fd445805068 100644
--- a/doc/emacs/package.texi
+++ b/doc/emacs/package.texi
@@ -490,8 +490,12 @@ startup if invoked with the @samp{-q} or @samp{--no-init-file} options
   To keep Emacs from automatically making packages available at
 startup, change the variable @code{package-enable-at-startup} to
 @code{nil}.  You must do this in the early init file, as the variable
-is read before loading the regular init file.  Currently this variable
-cannot be set via Customize.
+is read before loading the regular init file.  Therefore, if you
+customize this variable via Customize, you should save your customized
+setting into your early init file.  To do this, set or change the value
+of the variable @code{custom-file} (@pxref{Saving Customizations}) to
+point to your early init file before saving the customized value of
+@code{package-enable-at-startup}.
 
 @findex package-quickstart-refresh
 @vindex package-quickstart
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index ab1731aeb54..8c915766e1c 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -174,7 +174,13 @@ with \"-q\").
 
 Even if the value is nil, you can type \\[package-initialize] to
 make installed packages available at any time, or you can
-call (package-activate-all) in your init-file."
+call (package-activate-all) in your init-file.
+
+Note that this variable must be set to a non-default value in
+your early-init file, as the variable's value is used before
+loading the regular init file.  Therefore, if you customize it
+via Customize, you should save your customized setting into
+your `early-init-file'."
   :type 'boolean
   :version "24.1")