From: Angelo Graziosi <angelo.graziosi@alice.it>
To: 22727@debbugs.gnu.org
Subject: bug#22727: Managing packages writes the user init file
Date: Thu, 18 Feb 2016 01:49:36 +0100 [thread overview]
Message-ID: <56C51520.6020205@alice.it> (raw)
I have noticed that just using
Options - Manage Emacs Packages
writes my init file. For example I find these additions in my case:
(custom-set-variables
;; custom-set-variables was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(package-selected-packages (quote (tabbar-ruler sr-speedbar))))
(custom-set-faces
;; custom-set-faces was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
)
I discovered this only casually..
I think this is not the right thing to do. Why an application should
write a file which belongs to the user?
Maybe there is a better way saving those additions in another file which
the use could customize, more or less as we do with the desktop file or
lock file. For example in my init.el file I have
;; Instead to save in ~/.projects.ede
(setq ede-project-placeholder-cache-file "~/.emacs.d/projects.ede")
;; Instead to save in ~/.emacs.desktop
(setq desktop-base-file-name "~/.emacs.d/desktop")
;; Instead to save in ~/.emacs.desktop.lock
(setq desktop-base-lock-name "~/.emacs.d/desktop.lock")
We could have something like this
;; Instead to save in ~/.emacs.packages_installed
(setq desktop-base-lock-name "~/.emacs.d/packages_installed")
This would be very useful.. :)
TIA,
Angelo.
next reply other threads:[~2016-02-18 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 0:49 Angelo Graziosi [this message]
2016-02-18 16:48 ` bug#22727: Managing packages writes the user init file Eli Zaretskii
2016-02-18 18:49 ` Angelo Graziosi
2016-02-18 20:29 ` Eli Zaretskii
2016-02-18 22:04 ` Angelo Graziosi
2016-02-19 6:36 ` Nicolas Richard
2016-02-19 9:40 ` 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=56C51520.6020205@alice.it \
--to=angelo.graziosi@alice.it \
--cc=22727@debbugs.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).