Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Moving News and Mail
Date: 16 Jan 2000 18:43:02 -0800	[thread overview]
Message-ID: <m2k8l91kqx.fsf@reader.ptw.com> (raw)


Group,

 I need a little advice and a kind of general subject.

I want to move Gnus' News and Mail directories to a new home on a
different disk and in web space.  There to setup some "webglimpse"
tools and have full searching in several ways.

I already know how to setup the webglimpse tools etc but what worries
me is the part of setting new directories for News and Mail..  I
realize there are variables that control where gnus writes its files
etc.

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?

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?



             reply	other threads:[~2000-01-17  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-17  2:43 Harry Putnam [this message]
2000-01-18 17:51 ` Jaap-Henk Hoepman
2000-01-19 13:00   ` Harry Putnam

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=m2k8l91kqx.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).