Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: info-gnus-english-mXXj517/zsQ@public.gmane.org
Subject: Re: Setting up gnus: read on local, store remote (but not on mailserver)
Date: Thu, 28 Feb 2013 17:30:04 +0000	[thread overview]
Message-ID: <87lia8bb37.fsf@riseup.net> (raw)
In-Reply-To: <857b9155-899d-4161-878b-c653877457b4@googlegroups.com>

Hi Martin,

supermiri123-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org writes:

> OK, I've *almost* got it working.  I did the following via customize:
>
> (gnus-home-directory "/scpc:YYY-UAZjL2UjQio@public.gmane.org:~")
> (message-directory "/scpc:YYY-UAZjL2UjQio@public.gmane.org:~/Mail/")
> (gnus-secondary-select-methods (quote ((nnml "" (nnml-marks-is-evil t)))))
>
> This let me read my old mail which is stored with nnml.  I had to set
> nnml-marks-is-evil because otherwise tramp would encode and decode
> every .marks file, which was annoying.
>
> However, the above does not let me read the archived mail stored with
> nnfolder. For these, the path is explicitely in my .newsrc.eld file.
> I tried to do
>
> (setq gnus-message-archive-method
>       '(nnfolder "archive"
> 		 (nnfolder-directory   "/scpc:YYY-UAZjL2UjQio@public.gmane.org:~/Mail/archive")
> 		 (nnfolder-active-file "/scpc:YYY-UAZjL2UjQio@public.gmane.org:~/Mail/archive/active")
> 		 (nnfolder-get-new-mail nil)
> 		 (nnfolder-inhibit-expiry t)
> 		 (nnfolder-marks-is-evil t)))
>
> but this had no effect (I guess it will only affect newly created
> archive folders).

I would say (despite the warnings in the ~/.newsrc.eld file) that you can
safely delete the line in your ~/.newsrc.eld where the nnfolder group is
defined.  For me it is a (setq gnus-server-alist ...) cell.  The new
nnfolder hierarchy should be detected from your settings.

Also, you might want to make sure that those old archive folders aren't
present but inactive.  Enter A A to see your entire list of available
groups from all backends (including nnfolder).  You might want to do
that to check before you try my idea above.

> In fact, I'd rather have no explicit paths in .newsrc.eld at all,
> because I do want to be able to use gnus by just taking the .emacs
> with me.
>
> Any ideas?

The mail-type backends including nnml and nnmaildir are *reasonably*
portable in that the NOV and marks are always included within the folder
itself, so that's all you really need to back up when changing systems.
But you can't eliminate .newsrc.eld completely, AFAIK, as it holds both
your group subscriptions and your marks for news-type backends
(including some mail systems that Gnus implements in a net-news-esque
way, like nnimap).  One idea you might think about is that all Gnus
directory variables inherit the `gnus-home-directory' variables, and
most backends inherit `gnus-directory'.  By setting these, you could
just move everything to the rsync/scpc address and hopefully everything
would just work.

I'm excited to here that remote nnml is mostly workable, though. :)  Is
the performance acceptable?

--
Regards,
WGG

      parent reply	other threads:[~2013-02-28 17:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 13:24 supermiri123
2013-02-25 15:03 ` W. Greenhouse
     [not found] ` <mailman.20803.1361804622.855.info-gnus-english@gnu.org>
2013-02-25 18:04   ` supermiri123
2013-02-25 19:36     ` W. Greenhouse
     [not found]     ` <mailman.20819.1361821041.855.info-gnus-english@gnu.org>
2013-02-25 20:34       ` supermiri123
2013-02-25 23:06         ` W. Greenhouse
     [not found]         ` <mailman.20848.1361833630.855.info-gnus-english@gnu.org>
2013-02-27  7:56           ` supermiri123
2013-02-27  9:17             ` supermiri123
2013-02-28 17:30             ` W. Greenhouse [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=87lia8bb37.fsf@riseup.net \
    --to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
    --cc=info-gnus-english-mXXj517/zsQ@public.gmane.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).