Gnus development mailing list
 help / color / mirror / Atom feed
From: "David Z. Maze" <dmaze@mit.edu>
Subject: Re: config issues...
Date: 27 Mar 2000 23:29:14 -0500	[thread overview]
Message-ID: <87r9cvogyt.fsf@donut.mit.edu> (raw)
In-Reply-To: <xo8u2hsgoo2.fsf@hasc.com>

Darcy Brockbank <darcy@hasc.com> writes:
DB> I'm noticing that in my ~/Mail directory, gnus has left a temporary
DB> file for each time it's read my mail spool. These all start with
DB> "Incoming" and have some digits and characters after.
DB> 
DB> Is there any way to get it to automatically delete these files?

Yup; see the variable `mail-source-delete-incoming'.  Even better,
don't use an alpha version of Gnus; the version you're using
(Pterodactyl Gnus 0.99) is an alpha version of the now-released 5.8.x
branch, with the most recent released version being Gnus 5.8.3.

-- 
David Maze             dmaze@mit.edu          http://www.mit.edu/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell



      reply	other threads:[~2000-03-28  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-27 20:10 Darcy Brockbank
2000-03-28  4:29 ` David Z. Maze [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=87r9cvogyt.fsf@donut.mit.edu \
    --to=dmaze@mit.edu \
    /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).