From: Glenn Morris <rgm@gnu.org>
To: frederik@ofb.net
Cc: 25819@debbugs.gnu.org
Subject: bug#25819: 25.1; Added by Package.el. Added by Package.el. Added by Package.el. Added by Package.el.
Date: Wed, 22 Feb 2017 14:28:27 -0500 [thread overview]
Message-ID: <p4poiaf2jo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20170221230422.GJ1204@ofb.net> (frederik@ofb.net's message of "Tue, 21 Feb 2017 15:04:22 -0800")
frederik@ofb.net wrote:
> root) My /root/.emacs looks something like this:
>
> (setenv "HOME" "/home/frederik/")
> (setq savehist-file "/root/.emacs-history")
> (load "~/.emacs")
> (setenv "HOME" "/root/")
>
> Obviously this does not contain a "(package-initialize)" line, so the
[...]
> I wasn't able to figure out why the "(package-initialize)" lines then
> get inserted in ~/.emacs rather than /root/.emacs, but I hope the
> above clues provide a good enough place for someone else to start
> debugging this.
I tested with:
/tmp/h1/.emacs:
(setenv "HOME" "/tmp/h2/")
(setq savehist-file "/tmp/h1/.emacs-history")
(load "~/.emacs")
(setenv "HOME" "/tmp/h1/")
/tmp/h2/.emacs:
(setq foo 99)
HOME=/tmp/h1 emacs-25.1
M-x package-initialize
and could not reproduce any problem.
The package lines get added to /tmp/h1/.emacs, once only.
If you don't feel like debugging further, you could just add a
commented out package-initialize line to /root/.emacs.
Somehow I don't think your problem is a common one. :)
next prev parent reply other threads:[~2017-02-22 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 20:14 bug#25819: 25.1; Added by Package.el. Added by Package.el. Added by Package.el. Added by Package.el frederik
2017-02-21 22:19 ` Glenn Morris
2017-02-21 23:04 ` frederik
2017-02-22 19:28 ` Glenn Morris [this message]
2017-02-22 20:48 ` frederik
2017-02-23 2:28 ` npostavs
2017-02-23 6:23 ` frederik
2017-02-26 16:18 ` npostavs
2017-02-23 2:47 ` Glenn Morris
2017-02-23 6:39 ` frederik
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=p4poiaf2jo.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25819@debbugs.gnu.org \
--cc=frederik@ofb.net \
/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.