From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: package-enable-at-startup can be set via Customize (it seems), despite what the manual says
Date: Sun, 24 Nov 2024 12:20:55 +0200 [thread overview]
Message-ID: <86bjy5j5ko.fsf@gnu.org> (raw)
In-Reply-To: <26434.64488.939687.129056@frac.u-strasbg.fr> (Alain.Cochard@unistra.fr)
> Date: Sun, 24 Nov 2024 11:11:52 +0100
> From: Alain.Cochard@unistra.fr
>
>
> I have emacs version: GNU Emacs 29.4 (build 1, x86_64-redhat-linux-gnu,
> GTK+ Version 3.24.42, cairo version 1.18.0) of 2024-07-16.
>
> In the Info manual for Emacs I see "This is the ‘GNU Emacs Manual’, updated
> for Emacs version 29.4"; so this seems consistent.
>
> In section "49.3 Package Installation", I see
>
> "To keep Emacs from automatically making packages available at startup,
> change the variable ‘package-enable-at-startup’ to ‘nil’. [...] Currently
> this variable cannot be set via Customize."
>
> but if I type 'C-h v package-enable-at-startup <RET>' I get:
>
> package-enable-at-startup is a variable defined in ‘package.el’. [...]
> You can customize this variable.
This has been updated for Emacs 30. The text now says:
To keep Emacs from automatically making packages available at
startup, change the variable ‘package-enable-at-startup’ to ‘nil’. You
must do this in the early init file, as the variable 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 ‘custom-file’ (*note Saving Customizations::) to point to your
early init file before saving the customized value of
‘package-enable-at-startup’.
next prev parent reply other threads:[~2024-11-24 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 10:11 package-enable-at-startup can be set via Customize (it seems), despite what the manual says Alain.Cochard
2024-11-24 10:20 ` Eli Zaretskii [this message]
2024-11-24 11:48 ` Alain.Cochard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bjy5j5ko.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).