From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Copying .emacs.d
Date: Thu, 26 May 2016 06:02:31 -0700 (PDT) [thread overview]
Message-ID: <9eb9a591-75b8-486a-bb7a-96963577e6c2@googlegroups.com> (raw)
In-Reply-To: <86eg8pgtct.fsf@student.uu.se>
On Thursday, May 26, 2016 at 1:10:24 PM UTC+5:30, Emanuel Berg wrote:
> Rusi writes:
>
> > Is it ok to copy over .emacs.d from one
> > machine to another (assume similar OS)?
> >
> > I am specifically thinking of packages and
> > elpa directory -- is there some kind of
> > fingerprinting or is it legitimate?
> >
> > Context: I'd like to setup one minimal box
> > for my students and then they can copy over
> > .emacs.d from there to their laptops
>
> There are several things to consider.
>
> With respect to technology:
>
> 1) If the packages save data in .emacs.d
> there is no saying how specific that
> data is.
>
> 2) The software is compiled - someone else
> can answer, if the Emacs byte compiler
> take external factors into account or if
> it is boxed to an Emacs version.
>
> 3) The state (metadata) of local package
> manager will at best refer to events
> that took place on another computer.
[For anyone else who finds this thread...]
I subsequently found http://emacs.stackexchange.com/questions/10577/export-emacs-installed-packages
which suggests (byte-recompile-directory "~/.emacs.d/elpa" 0 t)
next prev parent reply other threads:[~2016-05-26 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 5:23 Copying .emacs.d Rusi
2016-05-26 7:40 ` Emanuel Berg
2016-05-26 13:02 ` Rusi [this message]
2016-06-03 1:08 ` Eric Brown
[not found] ` <mailman.741.1464916120.1216.help-gnu-emacs@gnu.org>
2016-06-03 1:20 ` Emanuel Berg
2016-06-03 3:00 ` Stefan Monnier
[not found] ` <mailman.746.1464922872.1216.help-gnu-emacs@gnu.org>
2016-06-03 5:22 ` Emanuel Berg
2016-06-03 16:54 ` Emacs at schools (was: Re: Copying .emacs.d) Emanuel Berg
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=9eb9a591-75b8-486a-bb7a-96963577e6c2@googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@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.
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).