From: Daniel Sauve <ahsdreamwalker@rogers.com>
Subject: Expire set up.
Date: Sun, 16 Jun 2002 16:18:32 GMT [thread overview]
Message-ID: <r8j7kxe8.fsf@rogers.com> (raw)
I think I figured how to do most of what I wish.
---
;; ---Begin Group parameter section, now!
(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))
;; 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")
;; This is so that I can obsesively keep e-mails from my GF,
;; family, and illuminatti contact.
("misc\\.personal\\..*"
;; Set expiry wait to never: Since there's an immediate option
;; as well, I figured that means "process this foo NOW" and
;; never means "don't touch this censored, or I'll sick ARM on
;; you".
;; Or something.
(expiry-wait . never)
(gnus-summary-line-format
"%U%R%z%I%(%[%d:%ub%-23,23f%]%) %s\n")
;; show me ALL my goodies, gran'ma.
(display . all))
;;; Why, yes, I do want my mailing lists to behave
("list\\..*"
;;;give me a week, I'll help take off the weight. Cause if I
;; haven't gone back to it in a week, I'm likely not gonna.
;; Besides, all the sane groups I'm on keep archives.
(expiry-wait . 7)
;; Sigh.... why do so many admins "break" their lists?
(broken-reply-to . t))
;; Slashdot daily mailers, Dailly Illuminators, words of the
;; day.... all daily thngs, archived elsewhere, that if I
;; don't read that, lose part of the point.
("announce\\..*"
(expiry-wait . 1)
;; --- End elisp
--
daniel
the delerious one, yo.
next reply other threads:[~2002-06-16 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 16:18 Daniel Sauve [this message]
2002-06-16 17:35 ` Frank Haun
[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=r8j7kxe8.fsf@rogers.com \
--to=ahsdreamwalker@rogers.com \
/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).