unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: emacs-devel@gnu.org
Subject: Re: Option to not automatically customize-save-variable `package-selected-packages'
Date: Thu, 18 Feb 2016 17:28:51 +0000	[thread overview]
Message-ID: <87vb5mudv0.fsf@yandex.com> (raw)
In-Reply-To: 831t8aufoe.fsf@gnu.org

>
>> My opinion now is in agreement with yours, John, and with Angelo in
>> that this should move to a dedicated file (though I originally
>> thought using the custom settings was a good idea).
>
> Please explain why you now think differently.
>
> Thanks.


Hope you don't mind me butting in. Perhaps the issue is not that Custom
is used by package.el but the way its used. For example, the old emacs
code browser (ecb) similarly added settings to Custom but the user was
alerted immediately and the old emacs init file backed up. All this
information was delivered to the user by a pop-up.

With package.el, unless you read the message buffer immediately after
list-packages, you'd never know that the init file had been edited.

Best.





  reply	other threads:[~2016-02-18 17:28 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 [this message]
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
     [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=87vb5mudv0.fsf@yandex.com \
    --to=m43cap@yandex.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).