Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Frank Haun <pille3000@gmx.net>
Subject: Re: Expire set up.
Date: Sun, 16 Jun 2002 19:35:39 +0200	[thread overview]
Message-ID: <86ofeb3z4k.fsf@pille.my-fqdn.de> (raw)
In-Reply-To: <r8j7kxe8.fsf@rogers.com>

Daniel Sauve <ahsdreamwalker@rogers.com> writes:

> I think I figured how to do most of what I wish.
> 
> 
> (setq gnus-parameters
>         ;; if all groups are total-expire, by all messages not
>         ;; unread,ticked or dormant are expired. Anything I give a low
>         ;;enough score to be marked read  will be expired. Will this
>         ;; set it for all groups? Did I miss the "proper (heh) way to
>         ;; set all to total expire?
>       '((".*\\..*"
> 	 (total-expire . t))

_*Really sure*_, you want this for _*all*_ groups? BTW, ".*" is enough
to match all groups.

>         ;; By setting expiry-wait, I can decide how long I have an
>         ;; article around. IE, here I've set the "no where else to put
>         ;; this" group misc.other to 3, so I have 3 days to decide how
>         ;; I want to treat mail from that sender.
> 	("misc\\.other*"
>          (expiry-wait . 3)
>         ;; I freely admit: I'm trying the example summary-line-format
>         ;; from the mannual just to see how it looks. <grin>
>          (gnus-summary-line-format
>           "%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
                                                  ^
                                                  |
Missing parenthesis (1x). -----------------------/

[...]

>         ("announce\\..*"
>          (expiry-wait . 1)
                            ^
                            |
Missing parenthesis (3x).--/

I'm not sure, but does Gnus/5.0808 know `gnus-parameters'?

Frank
-- 
  line-move: End of buffer [42 times]


  reply	other threads:[~2002-06-16 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-16 16:18 Daniel Sauve
2002-06-16 17:35 ` Frank Haun [this message]
     [not found] ` <vafy9dfm66m.fsf@lucy.cs.uni-dortmund.de>
     [not found]   ` <ptyqa831.fsf@rogers.com>
     [not found]     ` <vafhek2b132.fsf@lucy.cs.uni-dortmund.de>
     [not found]       ` <yqujit32mgvb.fsf@chaapala-lnx2.cisco.com>
     [not found]         ` <yleldqmfw3.fsf@windlord.stanford.edu>
2002-07-26 19:47           ` Glyn Millington

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=86ofeb3z4k.fsf@pille.my-fqdn.de \
    --to=pille3000@gmx.net \
    --cc=fhaun@wtal.de \
    /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).