From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: ...slow... saving with default gcc archiving...
Date: 20 Jun 1996 10:35:44 +0200 [thread overview]
Message-ID: <x6k9x2swin.fsf@eyesore.no> (raw)
In-Reply-To: Erik Selberg's message of 03 Jun 1996 19:07:29 -0700
Erik Selberg <selberg@cs.washington.edu> writes:
> I did some checking into this... I'm using the "default" Gcc'ing,
> which means when I send a mail message, a copy is saved into the file
> misc-mail which looks like mbox format. Anyway, this file gets _big_
> quickly, and consequentially everytime I save a file, I end up
> opening, appending, and saving this 10M file. Takes a couple seconds.
>
> Is there some way of improving this? Either by having misc-mail be
> nnml instead of the one file? Or by breaking misc-mail automatically?
>From the manual:
(setq gnus-message-archive-group
'((if (message-news-p)
"misc-news"
(concat "mail." (format-time-string
"%Y-%m" (current-time))))))
This will create a new archive group for each month's worth of
outgoing mail.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-06-20 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-04 2:07 Erik Selberg
1996-06-20 8:35 ` Lars Magne Ingebrigtsen [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=x6k9x2swin.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).