Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: ding@gnus.org
Subject: Re: many IncomingXXXXX files left in ~/Mail
Date: Fri, 04 Jan 2008 11:38:26 -0800	[thread overview]
Message-ID: <200801041938.m04Jcexj015326@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <v9k5mpwihc.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 04 Jan 2008 19:31:11 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

  > On Fri, Jan 04 2008, Dan Nicolaescu wrote:
  > 
  > > After emacs CVS HEAD switched to used gnus 5.13 I started seeing a lot
  > > of IncomingXXXXX files in ~/Mail. I get my mail from /var/spool/mail. I
  > > use nnml. 
  > > I don't know if those are for all the messages I receive, or just a part
  > > of them. 
  > > But something seems to not be able to clean up.
  > 
  > Set `mail-source-delete-incoming' to a number (or even to t, if you
  > are brave enough):
  > 
  > ,----[ <f1> v mail-source-delete-incoming RET ]
  > | mail-source-delete-incoming is a variable defined in `mail-source.el'.
  > | Its value is 4
  > | 
  > | Documentation:
  > | *If non-nil, delete incoming files after handling.
  > | If t, delete immediately, if nil, never delete.  If a positive number, delete
  > | files older than number of days.
  > | 
  > | You can customize this variable.
  > `----
  > 
  > See also (info "(gnus)Mail Source Customization").
  > 
  > Not deleting the incoming files is intended for the development
  > version.  
  > 
  > Although I wouldn't mind to change it to some number, say 7
  > or 14 days.  This question came up quite often recently.  Opinions?

Please do. I don't think most people want to think about setting yet
another variable, and remember to remove it later.


  > ,----[ (info "(gnus)Gnus Development") ]
  > |    Some variable defaults differ between alpha Gnusae and released
  > | Gnusae.  In particular, `mail-source-delete-incoming' defaults to `nil'
  > | in alpha Gnusae and `t' in released Gnusae.  This is to prevent lossage
  > | of mail if an alpha release hiccups while handling the mail.
  > `----

It might be a good idea to post such info to emacs-devel when new
versions are merged in CVS HEAD, one can't read all the patches to the
docs to find out about things like this.



  reply	other threads:[~2008-01-04 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 18:20 Dan Nicolaescu
2008-01-04 18:30 ` Leo
2008-01-04 18:31 ` Reiner Steib
2008-01-04 19:38   ` Dan Nicolaescu [this message]
2008-01-04 23:49     ` Reiner Steib
2008-01-05  0:52       ` Bastien
2008-02-16 13:04       ` Reiner Steib
2008-01-04 23:58   ` Adam Sjøgren

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=200801041938.m04Jcexj015326@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=ding@gnus.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).