From: Angelo Graziosi <angelo.graziosi@alice.it>
To: raman <raman@google.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Option to not automatically customize-save-variable `package-selected-packages'
Date: Thu, 18 Feb 2016 19:55:25 +0100 [thread overview]
Message-ID: <56C6139D.4020208@alice.it> (raw)
In-Reply-To: <p91io1mq9d6.fsf@google.com>
Maybe I am wrong but Aquamacs does this way. It saves all things in
(custom-set-variables
...
)
in another file..
Angelo
Il 18/02/2016 17:19, raman ha scritto:
> John Wiegley <jwiegley@gmail.com> writes:
>
> In general it's a good idea to put all custom settings in a separate
> file -- rather than the init file. As power user I've done this ever
> since I started using custom, since I wanted to be able to continue
> editing my init file by hand -- but it's a usage style that could
> perhaps be made the default -- since most casual users never discover
> this. Also, the persisted custom settings get flaky/fragile over time
> -- I've never filed a bug because it's hard to track down -- but over
> time you see things get truncated -- eg vars whose saved value is a long
> list. I presently keep my .customize-emacs file under git (I also
> encrypt it so passwds etc are not visible -- but that's a different
> story
>
> ) >>>>>> Angelo Graziosi <angelo.graziosi@alice.it> writes:
>>
>>> Since this was added to Emacs, I have a backup copy of my original init file
>>> so that I can remove those not requested addictions.. and this is very
>>> annoying...
>>
>> Angelo, would you open a bug on this matter so that we can track it properly,
>> and you'll be included on the discussion? I do think this should be fixed by
>> saving the settings to a separate file -- at least, based on this cursory
>> discussion. Perhaps the experts in this area have better reasons than we've
>> heard so far.
>
next prev parent reply other threads:[~2016-02-18 18:55 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
[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 [this message]
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=56C6139D.4020208@alice.it \
--to=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
/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.