unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: frederik@ofb.net
To: Glenn Morris <rgm@gnu.org>
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 12:48:53 -0800	[thread overview]
Message-ID: <20170222204852.GN1204@ofb.net> (raw)
In-Reply-To: <p4poiaf2jo.fsf@fencepost.gnu.org>

On Wed, Feb 22, 2017 at 02:28:27PM -0500, Glenn Morris wrote:
> 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. :)

You don't think my problem is common!? :) Well I'm not sure how other
people edit files as root, but after a few incarnations I decided that
a barebones /root/.emacs pointing to ~/.emacs is the best way to go.

Thank you (indeed) for taking the time to trim down my problem to a
minimal test case. If we make it a little less minimal:

/tmp/h2/.emacs:
    (setq foo 99)
    (package-initialize)

then I find it reproduces the problem:

/tmp/h2/.emacs:
    ;; Added by Package.el.  This must come before configurations of
    ;; installed packages.  Don't delete this line.  If you don't want it,
    ;; just comment it out by adding a semicolon to the start of the line.
    ;; You may delete these explanatory comments.
    (package-initialize)

    (setq foo 99)
    (package-initialize)

Thanks,

Frederick





  reply	other threads:[~2017-02-22 20:48 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
2017-02-22 20:48       ` frederik [this message]
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

  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=20170222204852.GN1204@ofb.net \
    --to=frederik@ofb.net \
    --cc=25819@debbugs.gnu.org \
    --cc=rgm@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).