Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Syncing Gnus (was: mail group by author?)
Date: Fri, 17 Apr 2009 15:27:36 +0200	[thread overview]
Message-ID: <kzprfbo1fb.fsf_-_@randomsample.de> (raw)
In-Reply-To: <87hc0nwlb5.fsf@uninett.no> (Vegard Vesterheim's message of "Fri, 17 Apr 2009 13:50:54 +0200")

Vegard Vesterheim <vegard.vesterheim@uninett.no> writes:
> I'm intrigued about the possibility for virtual folders in
> archiveopteryx, I hope to get a chance to try this soon.

Please let me know how this works out for you.

> I typically use several different computers, so I prefer a server-side
> solution. One of my biggest gripes about Gnus is that some
> meta-information (.newsrc.eld etc.) is stored on the client instead of
> the server. This means that the count of unread messages typically is
> wrong when I move from one computer to another.
>
> Yes, I know about solutions like this:
> http://www.emacswiki.org/emacs/GnusSync

Maybe the following is helpful:

- Tramp:

In your .emacs set:

(require 'gnus-load)
(require 'message)
(setq gnus-startup-file "/scpx:login@server:.newsrc")
(setq message-directory "/scpx:login@server:Mail/")
(setq gnus-directory "/scpx:login@server:News/")

Disclaimer: I've only tested this very shortly, so I'm not sure if this
is working correctly.

To speed this up, set up a ssh master connection beforehand (e.g. do
"ssh -f -N -M login@server" in the shell and specify ControlMaster for
the host in your .ssh/config). Otherwise, it will not only be dead slow,
but might also raise some administrator's eyebrows.

One day there might even be IMAP storage in Tramp. :-)

- sshfs:

http://fuse.sourceforge.net/sshfs.html

Mount single directory using sshfs and again set gnus-startup-file,
message-directory and gnus-directory accordingly. Never tried this, but
I don't see why this shouldn't just work.

Needless to say, both these methods are slower than just using rsync,
which is why I prefer the latter.

-David



  reply	other threads:[~2009-04-17 13:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  9:22 mail group by author? Stephen Berman
2009-03-30 11:57 ` David Engster
2009-03-30 12:49   ` Tassilo Horn
2009-03-30 13:13     ` David Engster
2009-03-30 15:25       ` Tassilo Horn
2009-03-30 15:59     ` Andreas Schwab
2009-03-31  6:42       ` Tassilo Horn
2009-03-31  9:18         ` David Engster
2009-03-31 10:36           ` Dovecot 1.2 virtual mailboxes (was: mail group by author?) Tassilo Horn
2009-03-31 11:35             ` Dovecot 1.2 virtual mailboxes David Engster
2009-03-31 12:23               ` Tassilo Horn
2009-03-31  9:52         ` mail group by author? Vegard Vesterheim
2009-03-31 10:25           ` Tassilo Horn
2009-04-14 16:39   ` Ted Zlatanov
2009-04-17  9:00     ` David Engster
2009-04-17 10:07       ` Vegard Vesterheim
2009-04-17 10:46         ` David Engster
2009-04-17 11:50           ` Vegard Vesterheim
2009-04-17 13:27             ` David Engster [this message]
2009-04-17 16:53       ` Ted Zlatanov
2009-04-17 20:15         ` Vegard Vesterheim
2009-04-17 20:42           ` Ted Zlatanov

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=kzprfbo1fb.fsf_-_@randomsample.de \
    --to=deng@randomsample.de \
    --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).