From: alex <current@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: johnw@gnu.org, emacs-devel@gnu.org, bruce.connor.am@gmail.com,
angelo.graziosi@alice.it
Subject: Re: Option to not automatically customize-save-variable `package-selected-packages'
Date: Thu, 18 Feb 2016 23:17:57 -0500 [thread overview]
Message-ID: <ixE_XmsOj7zk3PuOrOlbULsInpSjanCdvn3C9adh9P2B-BEerL60W1xmR2PFgh5B40E1N0hgIo9_NO9qa0TjxQ==@protonmail.com> (raw)
In-Reply-To: <831t8aufoe.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> This seems to be a general complaint about package.el using Custom to
> save the data about installed packages. I see no arguments as to why
> it's wrong to use Custom for that.
There's two major issues that I have in this instance:
1) The user is barely notified that the variable is being saved. In other instances (such as the Customize interface), it's quite obvious that it's going to change your customize file. Installing/upgrading packages changes the file with no obvious notice or prompt (as the notice gets drowned out by the package install/upgrade/delete messages). It's also not obvious at all that your customize file is going to change from those actions (it hasn't since these actions were created).
2) The package list for a particular user can differ between different machines. This makes it annoying to share a config among the machine with something like git. I think this data would be better suited to a separate place where it's easy go gitignore it, like with abbrevs, recentf and so on. It's tied not only to the customization in the init file but also outside state (that is, any packages installed/deleted outside of your init file).
[-- Attachment #2: Type: text/html, Size: 1439 bytes --]
next prev parent reply other threads:[~2016-02-19 4:17 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
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 [this message]
[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
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='ixE_XmsOj7zk3PuOrOlbULsInpSjanCdvn3C9adh9P2B-BEerL60W1xmR2PFgh5B40E1N0hgIo9_NO9qa0TjxQ==@protonmail.com' \
--to=current@protonmail.com \
--cc=angelo.graziosi@alice.it \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).