Gnus development mailing list
 help / color / mirror / Atom feed
From: Lee Willis <lee@gbdirect.co.uk>
Subject: Re: temporary files left behind by nnfolder
Date: 07 Dec 1998 12:47:12 +0000	[thread overview]
Message-ID: <lzzp906rvz.fsf@landlord.gbdirect.co.uk> (raw)
In-Reply-To: <3or9ucqgbf.fsf@neem.cam-orl.co.uk>

Sai-Lai Lo <S.Lo@orl.co.uk> writes:

> Not long ago I began to try out pgnus. One thing I noticed since the
> changeover is that in my nnfolder-directory, there are lots of Incoming*
> files. It seems that these files are created every time pgnus fetch mail
> from incoming mail folders in nnmail-procmail-directory. I guess these are
> temporary files which normally would be deleted. But for some reason they are
> left behind.

They are deleted in the *normal* run of things. Pgnus is not considered
'normal' for this purpose however. The reason being the pgnus is a
development version and despite the fact that no version of gnus has
lost mail since donkeys ago Lars always sets the appropriate stuff so
that the Incoming files are preserved in development releases.

> I hope I've provided sufficent information for the bug(?) to be reproduced.

s/bug/feature

If you want to get rid of these files you have several options ;

a) delete them by hand whenever you feel like (Though not while gnus is
checking for new mail ...)
b) Set up a cron job to delete them
c) Change line 417 of nnmail.el to

(defcustom nnmail-delete-incoming t

and recompile :)

HTH
Lee.
-- 
I was doing object-oriented assembly at 1 year old ...  
For some reason my mom insists on calling it "Playing with blocks"


  reply	other threads:[~1998-12-07 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-07 12:36 Sai-Lai Lo
1998-12-07 12:47 ` Lee Willis [this message]
1998-12-07 17:19   ` Christian Kurz

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=lzzp906rvz.fsf@landlord.gbdirect.co.uk \
    --to=lee@gbdirect.co.uk \
    /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).