Gnus development mailing list
 help / color / mirror / Atom feed
From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: ding@gnus.org
Subject: Re: Gnus Own-Cloudy?
Date: Tue, 10 Feb 2015 10:31:00 -0500	[thread overview]
Message-ID: <87386dokaz.fsf@yale.edu> (raw)
In-Reply-To: <87iofawbcb.fsf@ericabrahamsen.net>

Eric Abrahamsen writes:
 
> Where else should I be looking?

I keep my gnus synchronized by moving the whole gnus directory to 
another place, and then synchronizing with git-annex

#+BEGIN_SRC emacs-lisp
  (setq gnus-home-directory "~/sync/gnus/") (setq 
  message-directory "~/sync/gnus/Mail/")
#+END_SRC

I do not know if when you synchronize, your files get "touched" 
but another issue to consider is that your local .newsrc might be 
newer than your "just-synchronized" .newsrc.eld, if so, gnus just 
reads the .newsrc. If you do not use another news client, you 
might prevent this by setting:

#+BEGIN_SRC emacs-lisp
  (setq gnus-save-newsrc-file nil)
  (setq gnus-read-newsrc-file nil)
#+END_SRC

Also, if you do not save gnus before closing emacs, maybe you also 
want to keep .newsrc-dribble synchronized. 

Best,
-- 
Jorge.




      parent reply	other threads:[~2015-02-10 15:31 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
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 [this message]

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=87386dokaz.fsf@yale.edu \
    --to=jorge.alfaro-murillo@yale.edu \
    --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).