From: Elena <egarrulo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Sharing Emacs customization across different workstations?
Date: Thu, 30 Jul 2009 09:39:17 -0700 (PDT) [thread overview]
Message-ID: <7fcb2e85-5ddb-4aab-9b66-2e3fd3098110@s15g2000yqs.googlegroups.com> (raw)
Hi,
how would you advice sharing Emacs customization across different
workstations?
I mean, I use Emacs both at work (Windows) and at home (Linux).
Currently, I keep customization locally, and use a USB stick and a
synchronization tool to transfer changes back and forth. I've thought
about using just the USB stick and referencing it from .emacs, but I
fear losing it, whilst local copies get backed up. That's just my
current way of managing things.
Would you advice differently?
Thanks.
next reply other threads:[~2009-07-30 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 16:39 Elena [this message]
2009-07-30 16:50 ` Sharing Emacs customization across different workstations? Olivier Sirven
2009-07-30 18:02 ` Nurullah Akkaya
[not found] ` <mailman.3510.1248976974.2239.help-gnu-emacs@gnu.org>
2009-07-30 19:17 ` Sébastien Vauban
2009-07-30 17:42 ` Peter Dyballa
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=7fcb2e85-5ddb-4aab-9b66-2e3fd3098110@s15g2000yqs.googlegroups.com \
--to=egarrulo@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).