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

On Fri, Jan 04 2008, Dan Nicolaescu wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>   > 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.

I'll wait a couple of days to hear more/other opinions.  

BTW, allowing an integer is rather new (2003-02-24), so it might make
sense to set it to a small integer value (1..3) also for stable
versions.  What do people think?

>   > ,----[ (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.

Well, this information is not really new.  According to gnus.texi,
this was the practice at least since 1999.  What is new for Emacs CVS
users is the fact, that a development version of Gnus is in Emacs CVS.

If we change it to an integer, I don't think such an info message to
emacs-devel is required.  But feel free post it if you disagree. :-)

In general, changes in No Gnus (5.12.x/5.13) compared to Oort Gnus
(5.10.x/5.11) should be documented in (info "(gnus)No Gnus") aka
etc/GNUS-NEWS.  Please report if anything important is missing there.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2008-01-04 23:49 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
2008-01-04 23:49     ` Reiner Steib [this message]
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=v91w8xw3q3.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=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).