From: Luca Ferrari <fluca1978@infinito.it>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: suggestion for portable emacs customizations
Date: Thu, 30 May 2013 10:04:09 +0200 [thread overview]
Message-ID: <CAKoxK+7bnXe2wfYg7PGUjW-F0r=bSxszSLokAYxpxS4g6TyftQ@mail.gmail.com> (raw)
Hi all,
I'm beginning to have a lot of virtual machines where I have to run
emacs, and I would like to have them all configured the same way with
the same extensions (e.g., autocomplete) and configurations. Is there
a smart way to provide a kind of "distribution" so that I can ease and
automate the configuration of the multiple installations?
The first thing was thinking about was to set up a ~/.emacs directory
will all the lisp extensions and to raw copy it, but there could be a
smarter way...
Any idea?
Thanks,
Luca
next reply other threads:[~2013-05-30 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 8:04 Luca Ferrari [this message]
2013-05-30 11:01 ` suggestion for portable emacs customizations Dmitry Gutov
2013-05-30 12:29 ` Luca Ferrari
[not found] <mailman.654.1369901061.22516.help-gnu-emacs@gnu.org>
2013-05-30 8:42 ` Fabrice Niessen
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='CAKoxK+7bnXe2wfYg7PGUjW-F0r=bSxszSLokAYxpxS4g6TyftQ@mail.gmail.com' \
--to=fluca1978@infinito.it \
--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).