From: alex <current@protonmail.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Option to not automatically customize-save-variable `package-selected-packages'?
Date: Tue, 16 Feb 2016 22:39:48 -0500 [thread overview]
Message-ID: <pnYT4PdXkR9nkJwiKRUmQG3O0eqqRtO16uYqsb6sHa1Mp8L9QVaE4u4vBT60QmPsNL5fI2klLXTwh3Pn-aBZ3Q==@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
Hello, the 25.0.91 pretest version seems great so far. I like the dependency tracking in package.el.
Unfortunately whenever I install/update packages, it saves `package-selected-packages' to my customize file. This is a bit annoying as I share my config with git across multiple machines that have different packages installed.
While I could alter the definition of `package--save-selected-packages' myself, I'd think it would be nicer if there was a user option to toggle this behaviour. The default initialization of `all non-dependencies' seems to be what I'd always want anyway.
[-- Attachment #2: Type: text/html, Size: 655 bytes --]
next reply other threads:[~2016-02-17 3:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 3:39 alex [this message]
2016-02-17 4:10 ` Option to not automatically customize-save-variable `package-selected-packages'? 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
-- strict thread matches above, loose matches on Subject: below --
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:45 ` 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
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='pnYT4PdXkR9nkJwiKRUmQG3O0eqqRtO16uYqsb6sHa1Mp8L9QVaE4u4vBT60QmPsNL5fI2klLXTwh3Pn-aBZ3Q==@protonmail.com' \
--to=current@protonmail.com \
--cc=emacs-devel@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).