Gnus development mailing list
 help / color / mirror / Atom feed
From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: How do I mark messages for deletion?
Date: Fri, 31 Oct 2003 12:26:24 -0500	[thread overview]
Message-ID: <u8zr80ts4hr.fsf@blackbird.MITRE.ORG> (raw)
In-Reply-To: <764qxpz6kv.fsf@newjersey.ppllc.com> (Jake Colman's message of "Fri, 31 Oct 2003 11:59:28 -0500")

>>>>> On Fri, 31 Oct 2003 11:59:28 -0500, Jake Colman
>>>>> <colman@ppllc.com> said:

>>>>> "NK" == Norbert Koch <viteno@xemacs.org> writes:
NK> Jake Colman <colman@ppllc.com> writes:
>>> Will gnus delete mail without an 'E' expiry mark?  Or is t only the expiry
>>> process that does it?

NK> If you activate total-expire for a group, every read (and unticked)
NK> message is put through the expiry mechanism.

Dormant articles are also ignored by expiry when you use total expire.

>>> While on the topic, I have never been clear on the difference between
>>> auto-expire and total-expire.  Can you maybe explain?

NK> Hmm, I haven't looked at the code, so I can't provide more information
NK> as the manual "(gnus)Expiring Mail":

NK> ,----
NK> | In a nutshell, "auto-expire" means that Gnus hits `E' for
NK> | you when you select an article.  And "total-expire" means that Gnus
NK> | considers all articles as expirable that are read.  So, in addition to
NK> | the articles marked `E', also the articles marked `r', `R', `O', `K',
NK> | `Y' and so on are considered expirable.
NK> `----

> Hmmmm.  So you use total-expire and only tick those you really want
> to keep.  

Or mark them dormant if you don't want to see them every time you
enter the group.  I realize that's sort of an abuse of the dormant
mark, which is really to flag a thread of interest but only show it
when there's new messages in the thread, but what the heck, it works.

> I guess that makes sense.  And you can always manully
> press 'E' to (eventually) expire messages that are not in a
> totall-expire (or auto-expire) group.

One caveat.  total-expire is dangerous.  If you're not careful about
what you tick you could easily lose mail you consider important.
Also, there have been bugs in the past in which marks were lost.  I
haven't been bit by any in a long time, but there may be some still
around or new ones introduced.  I believe it is still the default to
add the expiry process in gnus-summary-exit-hook.  I recommend
removing that and periodically running expiry by hand in the group
buffer with gnus-group-expire-all-groups.  It also helps to have a
group line format that lists the number of ticked/dormant articles so
you can see if you've lost them.  That combo has saved me from going
to tape on numerous occasions.

-- 
Dave Goldberg
david.goldberg6@verizon.net





  reply	other threads:[~2003-10-31 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31 14:31 Jake Colman
2003-10-31 14:42 ` Norbert Koch
2003-10-31 15:38   ` Jake Colman
2003-10-31 15:58     ` Norbert Koch
2003-10-31 16:59       ` Jake Colman
2003-10-31 17:26         ` David S Goldberg [this message]
2003-10-31 17:41           ` Norbert Koch
2003-10-31 14:58 ` Jody Klymak

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=u8zr80ts4hr.fsf@blackbird.MITRE.ORG \
    --to=david.goldberg6@verizon.net \
    /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).