From: Leo <sdl.web@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: gnus-message-archive-group is too big!
Date: Tue, 05 Jun 2007 11:10:09 +0100 [thread overview]
Message-ID: <m2vee2af0e.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <m3bqfu4uko.fsf@ieee.org>
----- Randy Yates (2007-06-05) wrote:-----
>> Randy Yates <yates@ieee.org> writes:
>>
>>> 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?
>
> Hello? Is this thing on???
>
> --RY
You can use a different backend that supports one message per file.
For example,
(setq gnus-message-archive-group
'((if (message-news-p)
"nnml:Sent-News"
"nnml:Sent-Mails")))
HTH,
--
Leo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)
prev parent reply other threads:[~2007-06-05 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 16:59 Randy Yates
2007-06-05 9:30 ` Randy Yates
2007-06-05 10:10 ` Leo [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=m2vee2af0e.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
--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).