Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexander Kotelnikov <sacha@myxomop.com>
Cc: ding@gnus.org
Subject: Re: total and auto expiry
Date: Thu, 13 Mar 2003 13:34:16 -0500	[thread overview]
Message-ID: <7ysmtrf74n.fsf@myxomop.com> (raw)
In-Reply-To: <84isunrxf7.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Thu, 13 Mar 2003 18:25:32 +0100")

>>>>> On Thu, 13 Mar 2003 18:25:32 +0100
>>>>> "KG" == Kai Großjohann <kai.grossjohann@uni-duisburg.de> wrote:
KG> 
KG> Alexander Kotelnikov <sacha@forexware.com> writes:
>> Does this mean that the only difference between actions that are taken
>> over groups matching 'total' and 'auto' it that the former will be
>> expired even if expiry-wait for it is 'never?
KG> 
KG> No.  I think setting expiry-wait to never means that nothing is
KG> expired.
KG> 
KG> Normally, you can mark a message as expirable by hitting `E'.
KG> 
KG> Auto-expire means that Gnus hits `E' for you.  Nothing more, nothing
KG> less.
KG> 
KG> Total-expire means that messages marked E are expirable, as always,
KG> but *also* messages marked r, R, Y, K and so on are considered
KG> expirable.

Thus the one difference is an article's mark. Its destiny, to be or
not to be expired, is the same, if group is matched with total or auto
variable.

This also means that "total" described as dangerous is not too much
more dangerous than "auto", isn't it?

KG> Adaptive scoring does not work with auto-expire because it depends on
KG> the different marks r, R, Y, K etc.  But using auto-expire means that
KG> messages will be marked E, instead.
KG> 
KG> It used to be that total-expire was slower than auto-expire.  I don't
KG> know whether this is still true.

So it can be advised to use total with adaptive scoring and auto
otherwise. At first approximation they are the same.

-- 
Alexander Kotelnikov
Saint-Petersburg, Russia



  reply	other threads:[~2003-03-13 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 14:50 Alexander Kotelnikov
2003-03-13 17:25 ` Kai Großjohann
2003-03-13 18:34   ` Alexander Kotelnikov [this message]
2003-03-13 18:54     ` David S Goldberg
2003-03-13 19:17     ` Kai Großjohann

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=7ysmtrf74n.fsf@myxomop.com \
    --to=sacha@myxomop.com \
    --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).