Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Randy Yates <yates@ieee.org>
To: info-gnus-english@gnu.org
Subject: gnus-message-archive-group is too big!
Date: Fri, 01 Jun 2007 12:59:35 -0400	[thread overview]
Message-ID: <m3ejkvzk3s.fsf@ieee.org> (raw)

I've set this variable to point to a file to store all outgoing messages. Unfortunately
it stores EVERYTHING in one long humoungous file. It's now over 100 MB long. It's taking
to long to access it.

Is there any cure for this short of moving it out of the directory so that gnus starts
a new file? That is, is there any automated way for gnus to split the file up?
-- 
%  Randy Yates                  % "She has an IQ of 1001, she has a jumpsuit
%% Fuquay-Varina, NC            %            on, and she's also a telephone."
%%% 919-577-9882                % 
%%%% <yates@ieee.org>           %        'Yours Truly, 2095', *Time*, ELO   
http://home.earthlink.net/~yatescr

             reply	other threads:[~2007-06-01 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 16:59 Randy Yates [this message]
2007-06-05  9:30 ` Randy Yates
2007-06-05 10:10   ` Leo

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=m3ejkvzk3s.fsf@ieee.org \
    --to=yates@ieee.org \
    --cc=info-gnus-english@gnu.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).