From: Harry Putnam <reader@newsguy.com>
Subject: Re: Moving News and Mail
Date: 19 Jan 2000 05:00:42 -0800 [thread overview]
Message-ID: <m2iu0q9pxh.fsf@reader.ptw.com> (raw)
In-Reply-To: Jaap-Henk Hoepman's message of "18 Jan 2000 18:51:00 +0100"
Jaap-Henk Hoepman <hoepman@cs.utwente.nl> writes:
> On 16 Jan 2000 18:43:02 -0800 Harry Putnam <reader@newsguy.com> writes:
> > But what will happen when I redo those Variables and start writing to
> > the new directories containing thousands of old messages. Will gnus
> > just continue without a stutter or will there be a sort of start over
> > of some kind? Is there some kind of proceedure I need to follow?
>
> I've just moved all my old mail directories to a new location, changed the
> required variables (nnfolder-directory and nnml-directory), and copied the
> .newsrc.eld file to my new home directory, and it all worked without problem.
Good to hear ... thanks
>
> > Webglimpse will be writing files in the gnus directories too.
> > .glimpse* files and other control files etc. They can be contained
> > inside a subdirectory for neatness, but will these directories bother
> > the unborn Oort inside of pgnus?
> From personal experience I can tell that gnus believes all/most
> stuff inside a > mail folder to be mail. If you create new files or
> directories, gnus may think > it is a new group or something. I found
> out the hard way when I tried to store > both nnfolder and nnml files
> in a single directory. Ouch! I'm not sure whether > certain filenames
> (e.g. starting with a dot) are ignored.
That would have been from both backends using the same gnus control
files I think. In my case I don't think gnus will care that a
separate subdir is in there long as it isn't in gnus control files
like 'active' or '.overview'
I haven't done this yet so don't know for sure.
Thanks for the input.
prev parent reply other threads:[~2000-01-19 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-17 2:43 Harry Putnam
2000-01-18 17:51 ` Jaap-Henk Hoepman
2000-01-19 13:00 ` Harry Putnam [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=m2iu0q9pxh.fsf@reader.ptw.com \
--to=reader@newsguy.com \
/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).