From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: Gnus Own-Cloudy?
Date: Tue, 10 Feb 2015 10:48:37 +0000 [thread overview]
Message-ID: <87wq3qm48q.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87mw4mukxr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 10 Feb 2015 18:20:48 +0800")
On Tuesday, 10 Feb 2015 at 18:20, Eric Abrahamsen wrote:
[...]
> Is there anything you're sync'ing beyond the files/directories that I
> mentioned in my first post?
Hi Eric,
So, my approach for synchronising is to have a single directory that is
synchronised, called very non-imaginatively "~/synced". In there, I have
(for gnus) three directories: News, Mail and dotfiles.
In my home directory, I have News symbolically linked to
~/synced/News. The same for Mail. I also have .newsrc.eld linked to
~/synced/dotfiles/newsrd.eld. Likewise for ~/.gnus.el.
Because I use the registery, I have ~/.gnus.registry.eioio linked to
~/synced/dotfiles/gnus.registry.eioio.
For completeness, I also have the following gnus variable defined:
(setq gnus-startup-file "~/synced/newsrc")
although I am not sure what effect this has but it's been in my .gnus.el
file for yonks...
I cannot see anything else that I synchronise.
However, my main motivation for synchronising gnus was/is to be able to
work offline so I use the gnus agent. Maybe this makes a difference?
For completeness, my sync routine is:
1. boot up and log in.
2. run unison to synchronise
3. work work work play work
a) if using gnus, every so often, execute gnus-agent-fetch-session
4. run unison
5. turn system off
and I do this on every system except for work desktop that is up 24/7
and is essentially the "server" for all my other systems. All
synchronisations of the home system, the laptop and the handheld are
with this office desktop system. Sort of a star configuration.
The gnus cloud initiative won't make much difference for me as gnus is
but one element that I synchronise. I have all my working files in
~/synced (around 14 GB) including research papers, email, org, talks,
code, blah blah blah. I use my various systems as a form of redundant
backup... but more importantly every system I have looks the same so I
can pick up any of them and get to work right away!
HTH,
eric
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.1 + Ma Gnus v0.12 + evil-git-bdeb602
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)
next prev parent reply other threads:[~2015-02-10 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 6:05 Eric Abrahamsen
2015-02-10 9:17 ` Eric S Fraga
2015-02-10 10:20 ` Eric Abrahamsen
2015-02-10 10:48 ` Eric S Fraga [this message]
2015-02-10 10:53 ` Eric Abrahamsen
2015-02-10 11:45 ` Eric S Fraga
2015-02-10 15:19 ` Jorge A. Alfaro-Murillo
2015-02-11 2:12 ` Eric Abrahamsen
2015-02-11 11:12 ` Eric S Fraga
2015-02-11 13:48 ` Dan Christensen
2015-02-13 5:26 ` Eric Abrahamsen
2015-02-13 5:52 ` Eric Abrahamsen
2015-02-13 14:57 ` Eric Abrahamsen
2015-02-14 13:48 ` Eric Abrahamsen
2015-02-18 11:12 ` [PATCH] " Eric Abrahamsen
2015-02-10 15:31 ` Jorge A. Alfaro-Murillo
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=87wq3qm48q.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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 NNTP newsgroup(s).