From: Eli Zaretskii <eliz@gnu.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: joostkremers@fastmail.fm, johnw@gnu.org, emacs-devel@gnu.org
Subject: Re: Option to not automatically customize-save-variable `package-selected-packages'
Date: Fri, 19 Feb 2016 20:50:42 +0200 [thread overview]
Message-ID: <83fuwor0u5.fsf@gnu.org> (raw)
In-Reply-To: <87r3g8366a.fsf@gmail.com> (message from Artur Malabarba on Fri, 19 Feb 2016 16:29:17 -0200)
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: joostkremers@fastmail.fm, johnw@gnu.org, emacs-devel@gnu.org
> Date: Fri, 19 Feb 2016 16:29:17 -0200
>
> Another complaint I see is “I don't want my custom (or init) file being
> programatically altered, for reason X”. These complaints don't want to
> manually keep track of their packages with a `setq'. They want
> package.el to keep working its magic automatically, but keep its hands
> off their custom files.
I tried to figure out why people feel like that about this particular
customization, but couldn't. I asked the question about that several
times, but either didn't get an answer, or didn't understand it. I'd
still like to understand what's so special about this particular
customization.
> This sentence is explaining why _regular custom variables_ don't have
> the problem that `package-selected-packages' has.
>
> - _Regular custom variables_ don't get saved to the custom file without
> explicit user request, so it's easy to turn them into `setq's (which
> is what you were discussing).
>
> - OTOH, `package-selected-packages' _does_ get saved without explicit
> request, so it's hard for the user to turn it into a `setq'.
Ah, okay, thanks. So preventing package.el from doing that should
solve at least part of the problem. Would someone please work on
that?
next prev parent reply other threads:[~2016-02-19 18:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 9:27 Option to not automatically customize-save-variable `package-selected-packages' Angelo Graziosi
2016-02-17 23:05 ` John Wiegley
2016-02-18 1:04 ` Angelo Graziosi
2016-02-18 1:43 ` Artur Malabarba
2016-02-18 16:49 ` Eli Zaretskii
2016-02-18 17:28 ` Colin Baxter
2016-02-18 17:35 ` Kaushal Modi
2016-02-18 18:06 ` Artur Malabarba
2016-02-18 18:15 ` Eli Zaretskii
2016-02-18 20:34 ` Joost Kremers
2016-02-18 21:00 ` Eli Zaretskii
2016-02-18 21:49 ` Joost Kremers
2016-02-19 9:31 ` Eli Zaretskii
2016-02-19 9:47 ` Angelo Graziosi
2016-02-19 13:04 ` Artur Malabarba
2016-02-19 15:50 ` Eli Zaretskii
2016-02-19 18:29 ` Artur Malabarba
2016-02-19 18:50 ` Eli Zaretskii [this message]
2016-02-19 19:05 ` Kaushal Modi
2016-02-19 20:34 ` Eli Zaretskii
2016-02-21 23:56 ` Joost Kremers
2016-02-22 0:10 ` John Wiegley
2016-02-22 3:37 ` Eli Zaretskii
2016-02-22 21:00 ` Bastian Beischer
2016-02-19 4:18 ` alex
2016-02-19 9:48 ` Eli Zaretskii
2016-02-19 21:15 ` alex
2016-02-20 7:53 ` Eli Zaretskii
2016-02-18 18:25 ` Mechanisms to persist information (Re: Option to not automatically customize-save-variable `package-selected-packages') Clément Pit--Claudel
2016-02-18 18:54 ` Mechanisms to persist information Eli Zaretskii
2016-02-18 19:22 ` Jonathan Leech-Pepin
2016-02-20 2:17 ` Mechanisms to persist information (Re: Option to not automatically customize-save-variable `package-selected-packages') John Wiegley
2016-02-20 4:44 ` Eric Abrahamsen
2016-02-18 18:45 ` Option to not automatically customize-save-variable `package-selected-packages' John Wiegley
2016-02-19 4:17 ` alex
[not found] ` <vYxebPyde_BnqKsA6mXLVX-_dj3rDIchNBYl3O1LxNhGCR7etgi0R4ZR7de5PU1TZXk9R4YsCjNxqkoh5lBR3Q==@protonmail.com>
2016-02-19 9:47 ` Eli Zaretskii
2016-02-19 22:55 ` alex
2016-02-20 8:27 ` Eli Zaretskii
2016-03-05 0:40 ` alex
2016-02-18 16:19 ` raman
2016-02-18 18:55 ` Angelo Graziosi
2016-02-18 19:00 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2016-02-17 3:39 Option to not automatically customize-save-variable `package-selected-packages'? alex
2016-02-17 4:10 ` John Wiegley
2016-02-17 10:02 ` Artur Malabarba
2016-02-18 16:52 ` Aaron Ecay
2016-02-17 12:43 ` Joost Kremers
2016-02-17 10:14 ` Colin Baxter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fuwor0u5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=joostkremers@fastmail.fm \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.